In this guide
  1. Write down what the inspection must cover
  2. Apply the free cap to discovered URLs
  3. Example: repair links to a retired pricing page
  4. Distinguish initial HTML from rendered content
  5. Interpret responses and directives through page purpose
  6. Retain a repeatable inspection and review renewal

Write down what the inspection must cover

Inventory the roles of pages that must be inspected: articles, categories, pricing explanations and language counterparts. Agree on start URL, permitted hosts, exclusions and timing with the owner, then observe load on a small run. Do not include an administrative or authenticated area without a relevant authorized purpose. Compare the discovered set with the publication inventory or sitemap. Investigate whether missing pages are unlinked, excluded or unreachable instead of treating one crawl as a complete list of public content. This record makes inspected and unverified scope distinguishable when the result reaches somebody who did not operate the crawler.

Apply the free cap to discovered URLs

The official comparison describes a 500-URL free crawl and a one-year paid licence. A hundred articles do not necessarily expose only a hundred URLs once assets, variants and redirects are discovered. Mark the completed boundary if a limited run stops. Excluding important pages to fit the allowance cannot turn that partial inspection into a whole-site audit. Where saving, configuration or JavaScript execution is required, verify the selected edition’s feature boundary as well as URL capacity. Purchase should address a specified inspection obstacle, not the emotional effect of seeing many warnings or a desire to appear more professional.

Example: repair links to a retired pricing page

Imagine a shared recommendation block on fifty articles pointing at a retired pricing URL. Inspect the common component before presenting fifty unrelated engineering tasks. Put a representative source, affected set, current response, intended destination and exceptions into one request. Even a working redirect can leave an anchor naming an obsolete plan, so inspect meaning too. After release, follow representative and exceptional paths and recrawl the affected set where needed. Fifty is an illustrative scope, not a product benchmark. Completion means the intended explanation is reached through an accurate recommendation, rather than merely that a warning disappears from a later export.

Distinguish initial HTML from rendered content

A JavaScript site can return different initial and rendered content. Record collection mode, wait conditions, device and consent state when comparing results. A URL found in only one mode is a reason to inspect the difference, not immediately a crawler fault. Distinguish content available through rendering from content requiring a person to click a control. Investigate Google’s own observed state separately through Search Console where available; a successful local render does not guarantee search appearance. Carry the configuration and remaining uncertainty into a focused rendering investigation instead of describing a general desktop crawl as an exact reproduction of Google’s indexing process.

Interpret responses and directives through page purpose

Broken destinations, redirects, noindex and canonical annotations are not one kind of issue. A retired page’s redirect or an excluded utility page may be intentional. An intended public pricing guide with noindex warrants inspection of its actual HTML and headers. Crawl permission is neither authentication nor a guarantee of indexing exclusion, so confidentiality needs its own access control. Put observed behavior, page purpose, reader impact and intended behavior together in the repair record. A vendor severity label can remain useful context, but it cannot decide your implementation priority without knowing which business or reader task the affected URL serves.

Retain a repeatable inspection and review renewal

Retain start URL, scope, exclusions, collection mode, execution date and necessary output before and after the repair. Ask whether another operator can repeat the investigation. Verify saving and reopening under the current licence and preserve the meaning of configuration as well as the exported list. Follow search-side treatment and traffic separately from functional acceptance; fewer warnings are not a measured ranking gain. After a major move ends, map the next year’s inspections to the annual renewal and assign a decision owner. Distinguishing a valuable past audit from a continuing paid requirement supports a rational renewal, smaller process or migration.

Official sources

Pricing, availability and feature limits can change. Check the linked official pages before subscribing.

How we compareAdvertising disclosure