Every check, one crawl, any site
Paste any website: a store on any platform, a content site, a SaaS marketing site. Shipwork crawls a set of your pages from outside your network and runs every check that fits what the site is.
Fetches a set of public pages, the sitemap and robots.txt. Saved to your account if you are signed in to a paid plan; shared only if you choose to share it. Prefer a document? Run the printable report.
How this works
The audit identifies the platform and what kind of site it is, then runs the checks that apply: reachability, indexation, robots.txt, sitemap health, structured data, canonicals, duplicate content, internal links, trust pages and AI crawler access. A store additionally gets catalogue, price and availability checks. A publisher gets freshness. Every finding names the exact page and the fix.
What a technical site audit checks
The audit identifies the site and platform, discovers a bounded set of public pages, and runs the checks that fit what it finds. The output can cover reachability, indexability, robots.txt, sitemap health, structured data, canonicals, duplicate content, internal links, trust pages and AI crawler access. Store audits add catalogue, price and availability checks; publisher sites can receive freshness checks. The exact checks vary with site type and available public data.
Each finding is tied to a page or site-level evidence and includes a suggested fix. The audit runs from outside your network, so it can surface responses that differ from a logged-in or trusted browser. It is not a full crawl of every URL on a large site, and not every check applies to every site.
- A bounded crawl seeded by public pages, links and sitemap URLs.
- Page response, indexation signals, canonical and structured data checks where available.
- Robots.txt, sitemap and internal-link evidence.
- Additional ecommerce or publisher checks when the site type supports them.
How to read audit findings and coverage
Findings are grouped by check area and carry severity. Errors identify issues marked as must-fix; warnings identify risks or improvements; informational results add context. Start with errors that affect important pages, then review warnings against your goals. A site-wide finding such as a missing sitemap reference needs a different fix from one product page returning an error.
The number of pages checked is coverage, not the total size of your website. A clean result means no issue was found in the checks and pages included in this run; it does not prove that every URL is perfect or that search engines agree. Review the evidence and any skipped or unavailable checks before drawing conclusions.
- Filter or inspect findings by severity and check area.
- Prioritize home, category, product or landing pages that matter to visitors and search.
- Use the named URL and suggested fix to locate the responsible template, plugin or server rule.
- Rerun after changes to confirm the sampled public response has changed.
Fix the highest-impact audit issues first
Fix reachability before polishing metadata: crawlers cannot use a page that returns an error or blocks access. Next resolve unintended noindex, robots blocks and canonical conflicts on pages you want indexed. Then address missing or stale sitemap entries, duplicate content signals, internal links and structured data. For stores, confirm product availability and price match what customers can purchase. The right order depends on which pages and findings appear in your report.
- Example canonical:
<link rel="canonical" href="https://example.com/products/blue-shirt">should point to the intended preferred URL, not an unrelated page. - Example robots block:
Disallow: /in a wildcard group can block the entire site; remove or narrow it only if the block is unintended. - Update the actual source of the problem, such as a template, SEO app, CDN rule or sitemap generator.
- Use the fix guides for Search Console errors and the focused tools below to verify individual systems.
Choose a focused check when you know the symptom
A broad audit is a useful first pass when you do not know where to start. A focused tool is better when the issue is already clear or you need to repeat one check after a targeted change. For example, a missing product in Merchant Center calls for a product URL and feed review; a sitemap fetch warning calls for inspecting the exact sitemap and its child files.
On hosted platforms, some settings live in themes, apps, or platform-managed files. Confirm where the public output comes from before editing it. The audit reports symptoms from the outside; it cannot always identify which installed app or account setting generated them.
- Feed check: live Shopify catalogue data.
- Product page check: outside responses for sampled product URLs.
- AI crawler check: robots.txt verdicts for named agents.
- Structured data check and sitemap check: focused markup and sitemap review.
Questions
What does this audit check?
Does it work on any platform?
Is anything stored?
What does a technical SEO audit include?
Can I run a free SEO audit without signing up?
How long does a website audit take?
Does a clean technical SEO audit mean my site will rank?
What is the difference between a site audit and a full crawl?
Prefer one check at a time: feed check · product pages · AI crawlers · structured data · sitemap · learn guides