surfup

Audit robots.txt and crawler access safely

Separate crawl blocking from indexing controls and verify the exact affected URLs.

Use the procedure on a representative sample, keep the evidence, and record the next action.

Check access without blocking useful pages

  • Fetch robots.txt for each host and protocol. Record user-agent groups, allow/disallow rules, sitemap declarations, and the change history.
  • List important canonical URLs and test whether crawling is allowed. Check that robots.txt is not being used to remove a page from the index.
  • Check login, staging, search, and filter URLs separately. Use robots.txt only to manage crawling of confirmed duplicate or low-value URL spaces; protect private pages with authentication.
  • Deploy a small change, fetch robots.txt again, test representative URLs in Search Console, and keep a rollback copy.

Primary sources

Latest materials

All materials

Practical articles and guides by SurfUp.

Guide · 10 min

“What is…” pages and AI answers: lost clicks or falling demand

A bank’s reference section lost 24% of visits as demand fell 13%. How to tell clicks lost to an AI block from falling demand and how to measure it.

Read
Guide · 8 min

Traffic dropped after a Google update

How to tell whether a traffic drop comes from a Google update, seasonality or a site fault. 2026 update timeline, a six-question check and a plan for the first 14 days.

Read
Guide · 9 min

Demand fell or the site lost: reconciling traffic with Wordstat

Demand for deposits fell 75%, traffic 37%; for cards demand −35%, traffic −63%. How to reconcile traffic with demand and not blame the site for the market.

Read