Read technical and on-page reports

Separate response, indexation, metadata, structured data, and performance findings.

01

Begin with access and response

Check response codes, redirect chains, blocked resources, robots rules, and sitemap coverage before polishing metadata. A page that cannot be fetched or indexed will not benefit from a rewritten title.

02

Review indexation signals as a set

Canonical tags, noindex directives, robots rules, hreflang, and sitemap inclusion can conflict. Inspect the complete combination on representative URLs before deciding which signal is wrong.

03

Treat content fields by template

Titles, descriptions, headings, structured data, and content length often fail in groups because one template creates them. Group affected URLs by page type so a single template correction can replace hundreds of manual edits.

04

Keep performance evidence dated

Core Web Vitals and lab checks describe different samples. Note device, date, URL group, and whether the result comes from field users or a controlled test before assigning a performance fix.

Apply the guideReturn to the evidence and complete one verifiable action.
Open the app ↗
Did this guide solve the task?No account or workspace data is recorded here.