🔍 Using Search Atlas with Noindex Staging Sites

🚧 Understanding the Noindex Constraint

If your staging site uses a noindex directive (for example, via a robots.txt disallow rule or a noindex meta tag), Search Atlas tools that rely on automated crawling — including Site Audit and content imports in Content Genius — cannot access or process that site. This is not a platform limitation you can work around with settings; it is a deliberate crawl block that prevents any crawler, including Search Atlas, from reading your pages.

This means that if your rebuilt site is live at a staging subdomain such as beta.snazzy.solutions but is set to noindex, the automated workflows described in some help resources will not work until the noindex restriction is lifted.

✅ What You Can and Cannot Do

It helps to know exactly where the boundary is before choosing a workflow:

• Cannot do: Run a Site Audit crawl against a noindex staging subdomain.
• Cannot do: Auto-import staging pages into Content Genius via URL crawl.
• Can do: Paste page content manually into Content Genius for AI-powered feedback.
• Can do: Use Content Genius to audit and optimise individual pages by entering copy directly.
• Can do: Run a full Site Audit and content review once the site is live and indexable, or once the noindex restriction is temporarily removed in a controlled way.

📋 Option 1 — Manual Content Review in Content Genius

This is the recommended approach when your staging site is noindex and you need pre-launch feedback on page quality, SEO signals, and content gaps.

1. Open Search Atlas and navigate to Content → Content Genius (What are we writing today?).
2. Create a new document or open an existing one.
3. Copy the text content from your staging page (title, headings, body copy, meta description).
4. Paste the content into the Content Genius editor.
5. Enter your target keyword and configure the settings as you would for any new piece of content.
6. Use the AI suggestions, content score, and NLP recommendations to identify gaps and improvements.
7. Repeat this process for each key page you want to review before launch.

While this approach requires more manual effort than an automated crawl, it gives you detailed, per-page feedback that is fully actionable before the site goes live.

🛠️ Option 2 — Temporarily Remove Noindex for Crawling

If your team can safely control access to the staging environment, you may choose to temporarily remove the noindex directive to allow a Site Audit crawl. Use this option only if your staging subdomain is password-protected or otherwise not publicly discoverable, so that search engines do not accidentally index incomplete content.

1. Work with your developer to remove or disable the noindex rule on the staging subdomain.
2. Ensure the subdomain is protected by HTTP authentication or IP restriction so it remains inaccessible to search engine bots during this window.
3. In Search Atlas, go to OTTO SEO → Site Audit in the left sidebar and add your staging subdomain as a new project.
4. Run the audit and review all flagged issues — broken links, missing meta tags, heading structure, page speed signals, and more.
5. Export or document the findings, then restore the noindex directive on the staging site before making anything public.
6. Apply all fixes to the staging build before your production launch.

This option gives you the full power of Site Audit but requires coordination with your development team and careful access controls.

🚀 Option 3 — Run a Full Audit Post-Launch

If neither manual review nor temporary crawl access is practical before launch, the most straightforward path is to launch the site, confirm indexing is enabled, and then immediately run a Site Audit in Search Atlas.

1. Before going live, make sure all noindex directives are removed from production pages you want indexed.
2. After launch, go to OTTO SEO → Site Audit in the left sidebar and create a new project using your live production domain.
3. Run the audit within the first day of launch to catch and fix any technical issues before they affect rankings.
4. Use Content Genius to review and optimise priority pages using the live URLs once they are crawlable.

Pairing a fast post-launch audit with pre-launch manual reviews in Content Genius gives you strong coverage at both stages.

⚡ Quick Reference — Which Workflow Fits Your Situation

• Need feedback now, site is noindex: Use manual copy-paste into Content Genius (Option 1).
• Can protect staging with a password and remove noindex temporarily: Run Site Audit on staging (Option 2).
• Launch is imminent and no access changes are possible: Plan a same-day post-launch audit (Option 3).

💬 Need Help?

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.