Before and after a migration
Record redirects, canonicals, internal paths, important templates, and crawl coverage before launch, then compare the new site against the same baseline.
Website Audit Tool for Technical SEO
Turn a full-site crawl into a page inventory, grouped findings, and a practical fix queue. Review crawlability, status codes, redirects, canonicals, metadata, headings, links, images, response time, structured data, and security signals—then recrawl to verify what changed.
Find Technical SEO Issues
Start with the URLs search engines and visitors need to reach. The Pages inventory puts responses, redirect destinations and crawl depth beside each URL, making a broken product route or inaccessible article easier to investigate.
- Separate successful pages, redirects, 4xx errors and 5xx server failures.
- Compare the requested URL with its final destination to spot unintended redirects.
- Use response time to investigate slow server responses; it is not a full page-speed measurement.
- Check crawl depth to find important pages buried in the internal-link structure.
/guides/seo200
Indexed
Audit Titles and Meta Descriptions
Repeated metadata can come from one shared template rather than hundreds of separate writing mistakes. Filter titles and descriptions, compare the affected URLs, and decide whether the fix belongs in the template or the page content.
- Find missing or empty titles and descriptions that leave a page without useful metadata.
- Review duplicate text across different pages to restore a distinct topic and purpose.
- Inspect character lengths and short or long values without treating a length threshold as a ranking rule.
example.com › guides
SEO · TitleDescription- /guidesCompleted
- /shopMissing
Check Headings and Content
See how each crawled page presents its main topic. Heading counts, word count and content ratio help distinguish an incomplete article from a concise contact page; pages with different purposes should not all follow the same content target.
- Locate missing, multiple or duplicated H1 headings.
- Inspect H2 coverage, empty headings and jumps in heading levels.
- Compare word count and content ratio within similar page templates.
- Investigate language mismatches between metadata and the page's main content.
ContentH1
H1linen shirt
H2linen clothing
Review Canonical URLs
Compare a page's canonical target with the final URL reached by the crawl. This is particularly useful after migrations or when filters and parameters create several versions of the same content.
- Identify missing canonical tags and targets that differ from the final URL.
- Inspect repeated canonical targets to distinguish deliberate consolidation from template mistakes.
- Use Index Status separately to check Google's reported indexing; a canonical tag does not prove a URL is indexed.
/shop?sort=new
/shop?filter=linen
/shop
example.com/shoprel="canonical"
Audit Internal and External Links
A failed destination tells you what broke; its source pages tell you where to fix it. The Links inventory connects each destination with the pages and anchors that reference it, including repeated navigation and footer links.
- Separate internal paths from external destinations and filter their response status.
- Trace one broken destination to every recorded source page.
- Review anchor text and rel attributes in their linking context.
- Inspect links that still point to redirects after a page has moved.
Source/guides
404
/old-pricing404/setup503
Audit Website Images
Review image URLs together with the pages that use them. A missing image in a shared product template can affect many URLs, while alt text needs a decision based on what the image communicates in each page.
- Find failed image responses and missing alt attributes.
- Inspect recorded width, height and srcset information.
- Trace shared image sources to their page usages before fixing a template or asset.
Check Structured Data Coverage
Find pages with detected JSON-LD or microdata and pages without detected schema. Use this inventory to review coverage by content type; detecting markup does not establish that it is valid or eligible for a rich result.
- Inspect JSON-LD and microdata counts beside each page URL.
- Choose markup that matches visible content, then validate representative pages with a dedicated structured-data validator.
{ }
ArticleJSON-LD@contextschema.org
@typeArticle
headlinelinen shirt
Inspect Security Headers
Check which crawled pages return common protective response headers. Missing-header filters help surface configuration differences; deciding the correct policy still requires understanding how the website loads its content.
- Review HSTS, Content-Security-Policy, X-Frame-Options and X-Content-Type-Options presence.
- Investigate shared response patterns; these checks are not a security certification or a direct ranking score.
HTTPS200
Content-Security-PolicyX-Content-Type-OptionsStrict-Transport-Security
Compare Website Crawls
Keep a completed crawl as the baseline for your next release or migration. Compare later snapshots to see whether the affected URLs changed, then turn filtered findings into a concrete handoff for developers or editors.
- Review new, remaining and resolved findings across completed crawls.
- Compare page totals and crawl settings so wider discovery is not mistaken for a regression.
- Export filtered Pages, Links or Images records as CSV or Excel.
Before62→After87
Talk about Website Audit Tool. With SEO MCP.
Connect your AI assistant to Screpy’s SEO MCP server. Ask about your latest completed crawl, inspect affected pages and turn technical SEO findings into a clear order of work.
- Screpy: Hello! Let’s look at Website Audit Tool for example.com. What would you like to know?
- You: Check Website Audit Tool for example.com. What should I fix first?
- Screpy: The latest completed crawl shows missing titles and broken internal links. Start with the affected pages, then inspect the evidence before making changes. Crawl findings: Missing titles: 3 pages. Broken internal links: 1 link.
- You: Turn that into a short action plan.
- Screpy: I’ll keep the evidence and recommendations separate. Review the findings, choose one change and check the results afterward. Your next steps: Review: Check the source and date of each finding.. Decide: Choose the first change to make.. Verify: Compare the results after the change..
- You: Can you explain the evidence in plain language?
- Screpy: Yes. Ask about a supported result and I can explain what it shows, where it comes from and what is still uncertain. Missing data stays unavailable; recommendations are not automatic fixes.
Turn crawl evidence into a verified fix.
A useful audit does not end with an issue count. Keep the crawl comparable, validate representative URLs, find the shared cause, and define what the next crawl should show.
-
Create a comparable crawl baseline
Confirm the starting URL, maximum URLs, crawl depth, JavaScript mode, access rules, and site version. The completed crawl becomes a dated snapshot—not a continuously changing view of the live site.
-
Investigate representative URLs
Open one affected URL and verify its response, rendered output, purpose, indexability, template, and business value before deciding that a filter represents a defect.
-
Group the root cause and owner
Separate an isolated editorial problem from a CMS content type, shared component, navigation rule, route, or site-wide configuration issue. Fix the pattern instead of editing every row independently.
-
Publish, recrawl, and verify
Inspect the public change, run another crawl with comparable settings, and confirm the affected percentage and URL pattern changed for the intended reason.
Run a website audit when the site changes—not only when traffic falls.
Technical regressions often begin with ordinary releases, content work, migrations, and shared-template edits. A crawl before and after the change gives the team evidence while the implementation context is still fresh.
After a redesign or release
Check whether shared layouts, routing, metadata, images, scripts, or security changes introduced a repeated issue across valuable pages.
During ongoing content growth
Keep new articles, landing pages, categories, and programmatic templates connected, crawlable, internally linked, and technically consistent.
Use crawl evidence beside Search Console, release history, server logs, and rendered pages to investigate what changed without assuming one audit signal caused the traffic movement.
Choose a page check or a full-site audit
Use the free checker for one live URL. Use Website Audit when you need a crawl snapshot, repeated-pattern analysis, source-page context, exports, and verification across the site.
Crawl many URLs as one project, investigate Pages, Links, and Images inventories, and verify site-wide fixes in a later snapshot.
Review the rendered metadata, headings, links, images, structured data, accessibility, and technical signals for one public URL.
Screpy documentation
Learn how to run a website audit
Follow the Screpy guide to review audit results, investigate affected URLs, prioritize issues, and verify fixes after a new crawl.
Related SEO guides
Learn the concepts behind this workflow and apply them with practical SEO guidance.
SEO
How AI Prioritizes Technical SEO Audit Findings
Learn how AI interprets crawl, search, and performance data to group technical SEO findings, estimate impact, and prioritize verification.
Read article SEO
SEO Audit With MCP Using Real Crawl Data
Run an SEO audit with MCP using saved crawl data. Learn how to verify page findings, prioritize repairs, and separate evidence from unsupported AI advice.
Read article SEO
11 Claude SEO Skill Packs for Research and Site Audits
Compare 11 Claude SEO skill packs by task, data requirements and costs, with practical workflows, installation guidance and checks for trustworthy output.
Read article SEO
How to Find Bottom-of-Funnel Keywords That Convert
Bottom-of-funnel keywords: spot pricing, vs, alternatives, and review modifiers, validate intent in SERPs, and map terms to pages built for sign-ups fast.
Read articleWebsite Audit FAQ
Understand crawl scope, JavaScript rendering, missing pages, issue counts, prioritization, comparison, reporting, and what a technical audit can—and cannot—prove.
How often should I run a website audit?
Run a full audit after major site changes, migrations, redesigns, and content updates. For active websites, recurring audits are useful because new technical issues can appear after routine releases and edits.
How should I prioritize website audit issues?
Start with problems that affect crawling, indexing, availability, or many important pages. Then consider page value, affected templates, search traffic, conversion impact, and the effort required to fix the underlying cause.
Why is an important page missing from the audit?
First check whether the URL returns usable HTML, allows ScrepyBot, is linked from a crawled page, falls within the selected depth and URL capacity, and avoids redirect loops, authentication, bot challenges, timeouts, or server errors.
Can Screpy find issues that repeat across many pages?
Yes. A site-wide crawl makes it easier to see when the same issue appears across templates, categories, or groups of URLs. This helps teams fix the underlying pattern instead of reviewing every page in isolation.
Can I share website audit results with my team or clients?
Yes. Screpy supports reports and exports so audit findings, completed work, and remaining issues are easier to communicate with teammates, clients, developers, and stakeholders.
What is the difference between a website audit and a single-page check?
A single-page check reviews one URL at a specific moment. A website audit crawls pages as one site, finds repeated patterns, compares URLs, and gives your team a site-wide workflow for prioritizing and monitoring fixes.
What does Screpy check in a website audit?
Screpy reviews crawl access, HTTP status codes, redirects, crawl depth, response time, metadata, headings, canonicals, content signals, structured data, social tags, security headers, internal and external links, images, and related technical findings across crawled pages.
Can I compare website audit results over time?
Yes. Treat completed crawls as dated snapshots and compare them with equivalent scope and settings. Review which findings were fixed, which remain, which are new, and whether the same page types and important URLs were included in both crawls.
Can Screpy audit websites that rely on JavaScript?
Screpy provides a JavaScript crawl setting for sites whose important links or content are created in the browser. JavaScript rendering does not bypass robots rules, authentication, bot protection, server errors, or the project crawl scope.
Why can the issue count increase after I fix the website?
A newer crawl may discover more pages, reach a previously blocked template, or use different scope settings. Compare the crawled-page total, affected percentage, URL patterns, crawl configuration, and site version before deciding whether website health improved or declined.
Does fixing every website audit finding guarantee higher rankings?
No. A website audit helps you investigate technical condition and verify implementation changes, but it does not guarantee rankings or traffic. Search outcomes also depend on relevance, content quality, authority, competition, demand, indexing, and how search engines interpret each page.
Exploring SI SEO?
Understand Super Intelligence terminology and connect website audits, search research, rankings, and AI visibility in one practical Screpy workflow.
Big on SEO. Light on Your Wallet.
A comprehensive SEO toolkit at a refreshingly affordable price.
- Technical audits, rank tracking & AI visibility
- Keyword research, backlinks & uptime monitoring
- One workspace. Flexible plans. Less to spend.
More stays in your pocket