Technical SEO for clear crawl and page intent.

A crawler lists what exists. An audit explains which findings matter for this site, in what order, and why. That requires combining the crawl with Search Console coverage, analytics, server logs and the commercial value of each template, then producing a prioritised set of changes with reproduction steps rather than a colour-coded list of every issue the tool can detect.

Crawled-currently-not-indexed usually signals a quality, duplication or selection judgement rather than a blocking error. Common causes are near-identical pages competing with each other, thin templated content, conflicting canonicals, or pages that add nothing beyond what an existing indexed URL already covers. The fix is normally consolidation or genuine differentiation, not a robots directive.

Rarely. For sites below a few thousand URLs Google generally crawls everything it considers worthwhile, and crawl budget is not the constraint. It becomes a real concern on large catalogues, faceted navigation, calendar or filter parameters, and sites generating URL combinations faster than they can earn crawl demand.

Compare the raw HTML response against the rendered DOM. Fetch the page without executing JavaScript and check whether the H1, body copy, internal links, canonical and structured data are present. If key content only appears after hydration, crawlers may see it late or inconsistently, and AI crawlers that do not execute JavaScript at all will see nothing.

It is the parsing of raw server access logs to see which URLs bots actually requested, how often, and what they received. It answers questions a crawl cannot: where crawl effort is wasted, which templates are ignored, and whether a fix changed real bot behaviour. It is most valuable above roughly 1,000 URLs and requires raw log access from your host.

Recrawl and reprocessing typically make indexation changes observable within a few weeks, faster for high-authority sites and slower for large or rarely crawled ones. Traffic and ranking effects take longer and depend on competition, content quality and factors outside the audit. No responsible technical audit can put a date on a ranking change.

Usually yes, at least for the blocking issues. Publishing into a site that cannot be crawled, rendered or indexed correctly wastes the content investment. Non-blocking optimisations — incremental speed work, refinement of structured data — can proceed in parallel with content production.

It is a precondition rather than a guarantee. AI crawlers need to fetch the page, receive content in the HTML response, and parse a coherent heading structure and entity set. Sites that depend on client-side rendering, block AI user agents in robots.txt, or hide key content behind interactions are frequently invisible to those systems regardless of content quality.