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.
Too Long; Didn't Read
Screpy Website Audit turns a completed crawl into Pages, Links, and Images inventories. Teams can investigate one URL, identify a repeated template or site-wide pattern, prioritize the underlying fix, export an implementation queue, and verify the public result in a later crawl.
Screpy keeps page, link, image, crawl, and search context connected. Each filter starts an investigation; the affected URL and its real purpose determine whether a change is needed.
See which URLs Screpy reached and what each request returned before treating a page-level signal as an SEO problem.
Review whether important pages present consistent indexing signals and whether preferred URLs remain accessible.
Find missing, duplicated, empty, short, long, or inconsistent page elements across individual URLs and shared templates.
Use page-purpose and template context to investigate content signals instead of trying to force every URL toward the same score.
Map each destination to the pages that reference it so broken paths, redirects, anchors, and attributes become actionable fixes.
Inspect image files, markup, and page usage together before changing accessibility text, dimensions, formats, or delivery.
Use crawl response time to find investigation candidates, then connect important URLs with dedicated page-speed and Core Web Vitals evidence.
Review markup and search-presentation signals on the pages where they apply without treating schema presence as a ranking guarantee.
Turn a completed crawl into a URL-level inventory. Compare the response, destination, crawl depth, metadata, headings, canonical, content, structured data, social tags, image findings, and security signals for each page.
Learn more about pages report
Review internal and external destinations with their response status, anchor text, attributes, usage count, and source pages. This turns a broken destination into a specific navigation, content, or shared-template fix.
Learn more about links report
Group crawled image sources and inspect response health, alt text, dimensions, responsive delivery, loading behavior, source type, and page usage before changing an asset or shared component.
Learn more about images report
Treat every completed crawl as a dated snapshot. Keep the scope and settings comparable, review what changed across important templates, and confirm that the intended finding moved without hiding a new problem elsewhere.
Learn more about crawl progress 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.
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.
Open one affected URL and verify its response, rendered output, purpose, indexability, template, and business value before deciding that a filter represents a defect.
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.
Inspect the public change, run another crawl with comparable settings, and confirm the affected percentage and URL pattern changed for the intended reason.
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.
Record redirects, canonicals, internal paths, important templates, and crawl coverage before launch, then compare the new site against the same baseline.
Check whether shared layouts, routing, metadata, images, scripts, or security changes introduced a repeated issue across valuable pages.
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.
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
Follow the Screpy guide to review audit results, investigate affected URLs, prioritize issues, and verify fixes after a new crawl.
Learn the concepts behind this workflow and apply them with practical SEO guidance.
An AI technical SEO audit analyzes crawl and performance data to flag indexation, redirects, broken links, and schema issues, then prioritizes fixes by impact.
Read articleLearn what a website analysis tool should measure, from bounce rate and conversions to traffic, rankings, sales, page issues, and optimization tasks.
Read articleGoogle AI Overviews appear for complex, informational, or comparison queries when Google finds a multi-source summary adds value beyond standard results.
Read articleAI visibility benchmarking reveals how your brand stacks up on mentions, citations, share of voice, and prompt gaps across leading AI search platforms.
Read articleUnderstand crawl scope, JavaScript rendering, missing pages, issue counts, prioritization, comparison, reporting, and what a technical audit can—and cannot—prove.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Yes. Screpy supports reports and exports so audit findings, completed work, and remaining issues are easier to communicate with teammates, clients, developers, and stakeholders.
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.
Explore how Screpy combines audits, rankings, AI visibility and monitoring, with clear plan limits.
