Page Explorer
Search, filter, and compare every crawled URL with its status, metadata, indexability, and issue count.
Example crawl · Sample data1,284pages crawled745issues found
Crawl important pages within a defined scope, trace technical issues to affected URLs, and turn the findings into a plan your team can verify.
Free to start · No credit card required
Move from the crawl to a decision without rebuilding the work in a spreadsheet.
Discover
Crawl eligible internal pages within the chosen scope and surface technical issues.
Prioritize
Focus on what affects the most URLs and carries the most risk.
Investigate
Trace each issue to affected URLs with clear evidence.
Verify
Compare runs and confirm that fixes close the loop.
The technical SEO audit guide walks through the checks and their evidence. For discovery problems, inspect the affected pages with Internal Link Analysis.
Keep the supporting details with every issue.
HighBroken internal linksLinks that return a 4xx or 5xx status.142Example crawlAffected · 142
MediumMissing canonicalPages without a self-referencing canonical tag.318Example crawlAffected · 318
MediumRedirect chainsURLs that redirect through multiple hops.76Example crawlAffected · 76
LowOrphan pagesPages with no internal links pointing to them.209Example crawlAffected · 209
Move from the overview to the exact pages and links.
Move from an issue group to the exact pages, link relationships, and site structure behind it. Each explorer keeps the crawl scope and evidence visible.
Page ExplorerSearch, filter, and compare every crawled URL with its status, metadata, indexability, and issue count.
Link ExplorerInspect source and target URLs, anchor context, link problems, and the relationships that shape internal authority.
Site TreeSee how directories and pages fit together so orphaned, over-deep, or weakly connected areas become easier to spot.
Link Explorer
Inspect source and target URLs, anchor context, link problems, and the relationships that shape internal authority.
Site Tree
See how directories and pages fit together so orphaned, over-deep, or weakly connected areas become easier to spot.
Use Site Audit for recurring SEO work as well as individual reports.
- Baseline
- +112 issues
- 38 fixed
- 27 fixed
- +3 issues
12 fixed
3 new
Take a finding through to a verified fix.
A useful audit does more than name problems. Crawl Foundry keeps the scope, supporting details, priorities, and next crawl connected so the team can check the result.
Set the scope
Choose the property, crawl boundaries, and run that should define the evidence.
Inspect the evidence
Open affected URLs, page details, and link relationships before deciding on a fix.
Choose the next action
Use Action Center priorities to focus on work with clear impact, effort, and supporting evidence.
Verify over time
Schedule the next crawl, compare changes, and receive alerts when important issues appear or return.
Questions before your first crawl?
What does Site Audit crawl?
Site Audit follows eligible internal pages within the configured scope and records technical, metadata, status, indexability, and linking evidence.
Can I compare audit runs?
Yes. Recurring runs make new, persistent, and resolved issue evidence visible over time.
How are issues prioritized?
Issues are grouped by severity, affected scope, and the evidence available for investigation. Crawl Foundry does not present a single score as objective truth.
Can agencies separate client sites?
Yes. Each client property stays within its own workspace and access boundary.
Technical SEO audit: from an affected URL to a checked correction
A technical SEO audit helps you decide which URLs need work and how to verify the result. Follow the example above: start with an affected URL, inspect the finding and choose a correction. Check that URL again after the change so the audit ends with a verified fix.
Set the crawl scope
Choose the site and the URLs you need to investigate. A bounded crawl produces findings for that scope; it is not proof that every URL on the website was checked.
Review the evidence at the URL
For a broken internal link, inspect the linking page, destination and response. For a canonical issue, compare the declared target with the page you want indexed before choosing a correction.
Verify the specific correction
After fixing the link or canonical, check the affected URLs again. A resolved technical finding confirms that correction; it does not by itself prove a ranking or traffic gain.
What is the difference between a crawl and an SEO audit?
A crawl collects URLs, responses and page signals. The audit organizes the findings so you can inspect evidence, set priorities and plan a correction.
Should I fix every warning immediately?
Start with findings that affect the pages and journeys you need. Confirm the evidence and expected behavior before changing a URL, redirect or canonical; a warning alone is not a diagnosis of lost traffic.
Using Site Audit
From domain verification to the audit report, this tour shows crawl settings, price review, live requests and how to examine technical issues in Crawl Foundry Site Audit.
The tour uses an example workspace. The app shows the current price before you start a paid request.
Try Crawl FoundryTurn every crawl into a clearer next move.
Free to start · No credit card required