Find the technical issues
behind your pages.
Check crawlability, indexability, canonicals, and on-page signals. See the evidence behind each finding and what to address next.
- /
- /about
- /services
- /teeth-whitening
- /pricing
- /blog
- /contact
Page details
sample-site.test/services/teeth-whitening
<head> excerpt (original)
<link rel="canonical" href="https://sample-site.test/services/whitening" /><title>Teeth Whitening | Sample Site</title>… </head><head> excerpt (rendered)
<link rel="canonical" href="https://sample-site.test/services/teeth-whitening" /><title>Teeth Whitening | Sample Site</title>… </head>Illustrative audit · Fictional website
How does Technical Audit work?
See how to review technical findings, check the evidence, and decide what to address next.
See what’s wrong.
Know where to start.
Group technical issues by severity and affected pages. Open a finding to see the evidence and a recommended next step.
Technical audit
sample-site.test
Broken internal links
6 pages link to a missing URL.
- Affected URL
/services/emergency-care404 Not found- Found on (examples)
/services/contact- Recommendation
- Update these links to the intended live page.
Broken internal links
6 pages link to a missing URL.
- Affected URL
/services/emergency-care404 Not found- Found on (examples)
/services/contact- Recommendation
- Update these links to the intended live page.
Illustrative audit · sample-site.test
Follow the link.
Find the break.
Trace redirects to the URLs behind them. See where the path breaks, and what needs to change.
- What happened
- Two URLs keep sending the request back to each other.
- Why it matters
- The redirect never reaches a page that can be crawled.
- What to review
- Choose the intended destination and remove the circular rule.
Illustrative redirect path · sample-site.test
Technical audit conversation
Using saved auditWhat should I review first?
Start with the redirect loop. The audit found /offers and /special-offers redirecting back to each other.
/offers → 301 → /special-offers/special-offers → 302 → /offersConfirm the intended destination, then remove the circular redirect rule.
Ask your audit
a better question.
Ask AI to explain saved findings, surface important issues, and suggest what to check next.
Illustrative conversation · sample-site.test
Questions you might have.
What does the technical audit check?
It reviews response codes, redirects, indexability, canonicals, titles, descriptions, headings, internal links, images, and sitemap signals. Findings include evidence and a recommended next step.
Can AI explain my audit findings?
Yes. Ask about a saved audit to review important findings, understand the evidence, and identify a useful next check.
Can it fix issues on my website?
The audit identifies findings and suggests what to investigate or change. It does not automatically change your website. You or your web team make and verify the changes.
Why compare original and rendered HTML?
JavaScript can change page elements after the original response is received. Comparing the two helps you see differences in titles, descriptions, headings, canonicals, directives, links, and visible content. These comparisons are available when rendered HTML is included in the audit.
Does every finding need to be fixed?
A finding still needs context. Severity and recommendations help you decide what to review, but you should confirm that a signal is unintended and relevant to the page before changing it.
Will fixing every issue improve rankings?
No audit can guarantee that. The report helps you identify technical signals to investigate; search visibility also depends on content, competition, and other factors beyond this audit.
Find the issue.
Plan your next fix.
Start with a technical audit. Review the evidence with your team or AI.
Audit your website