On a small site you can fix pages one by one. On a large site the template is either your biggest lever or your biggest problem.
None of these are content problems. They show up when thousands of pages inherit the same mistake.
One wrong block in a product or article template multiplies across every page that uses it.
If content only appears after heavy JS, many crawlers and some AI systems see an empty shell.
Engineers ship weekly. SEO checks run monthly, if at all. Drift happens in that gap.
Parameter URLs, old filters and thin variants crowd out the pages that should be ranking.
Six teams touch the site. Nobody owns the search consequences of a change made at 5pm on Friday.
Stakeholders need numbers they trust, tied to pipeline conversations, not vanity charts in a monthly PDF.
Fixing 40 product pages by hand is theatre. Fixing the template they all share is the job. We audit for patterns, write clear tickets your developers can act on, and prioritize by how many URLs each fix affects.
For migrations and redesigns we are in the room before launch, not after the traffic drop. For ongoing work we agree a release checklist so SEO does not depend on someone remembering. The output is boring on purpose: fewer surprises, measurable coverage, reports you can defend in a budget meeting.
Large sites need a diagnosis that covers templates, rendering, index health and process, not a keyword list.