Forum category

Technical SEO

Crawling, rendering, indexation, schema, performance, international targeting, and technical diagnosis.

Technical SEO is where a site either earns its crawl budget or quietly wastes it. This category covers the mechanics that decide whether a page can be fetched, rendered, understood, and served. Status codes, redirects, canonical choice, structured data, hreflang, Core Web Vitals, and the rendering path a framework puts between content and a crawler all belong here.

The discussions that work best here start with an observation and a measurement, not a theory. A page that dropped out of the index, a template that renders empty without JavaScript, a redirect chain that appeared after a migration: all of those are answerable. "Is technical SEO still important" is not.

What belongs here

  • Status codes, redirect chains, and the aftermath of a migration
  • Canonical conflicts, parameter handling, and duplicate templates
  • Rendering questions, hydration gaps, and server side versus client side output
  • Structured data validation, eligibility, and rich result loss
  • Core Web Vitals field data that disagrees with lab data
  • International targeting, hreflang reciprocity, and country selection

Bring this with your question

  • The exact URL, or a representative URL if the pattern repeats
  • What the browser sees compared with what a fetch without JavaScript returns
  • The response headers, including any canonical or robots directive
  • The date the behavior changed, and what shipped around that date
Indexability breakdown for a 395 URL crawl showing 324 indexable pages and 71 non indexable pages.
A crawl separates indexable pages from the rest before anyone argues about rankings. Bringing this kind of split to a question saves the first three replies. Swipe the panel to read it at full width.

Approved discussions

1 discussion