SEO & Marketing
Website Release Doctor
Crawl a website before or after deployment, find technical release blockers, prepare exact fixes, and verify what changed without creating an account.
Preparing the release cockpit…
Share this tool
Referencing this tool on a website?
Copy an attribution link. It is optional and does not change free access.
Transparent methodology
What the result includes—and what it does not
Built for developers, site owners and SEO teams checking a public launch, deployment or migration without installing a desktop crawler.
Calculation method
- 1The browser coordinates small requests to SolveKit's own Cloudflare Worker. The Worker accepts only public HTTP and HTTPS URLs, follows a limited redirect chain and rejects credentials, local addresses and non-web ports.
- 2The first batch reads robots.txt and declared or conventional sitemaps. Later batches crawl same-host links and sitemap URLs up to the limit you choose; no fetched HTML is retained in the project file.
- 3Each page is tested for access, redirects, robots directives, canonical, title, description, language, viewport, headings, Open Graph, JSON-LD, mixed content and visible initial-HTML text.
- 4Page findings are crossed across the crawl to expose repeated titles and canonicals, sitemap/indexability conflicts and template-like path groups. The verdict is based on evidence and severity, never an opaque score.
Assumptions and limits
- Ready to ship means that no blocker was detected inside the checked public scope. It does not guarantee indexing, ranking, rich results, browser rendering equivalence or availability from every network.
- The current release reads the initial HTTP response. JavaScript-rendered DOM comparison, authenticated staging, PageSpeed, scheduled monitoring and ownership-based 5,000-URL projects remain later phases.
- The general robots group is interpreted for crawl planning. Search engines can select more specific groups, support different directives and make their own canonical or indexing decisions.
- A 500-URL check runs as respectful batches and can take time. A target site can rate-limit or block the identifiable SolveKit crawler at any point.
Worked example
Catch a staging noindex before launch
Input: A 120-page production domain whose product template still returns X-Robots-Tag: noindex.
Output: Block release, one grouped root cause, all affected URLs, the response evidence and a project to prove the directive disappeared after deployment.
Primary sources
- Google Search — Crawling and indexingPrimary documentation for crawl access, indexability signals, canonicals, sitemaps, redirects and JavaScript search behavior.
- Google Search — robots.txtExplains that robots.txt primarily controls crawling and is not a guaranteed removal mechanism.
- Google Search — Canonical URLsOfficial guidance for canonical signals and duplicate URL consolidation.
- Sitemaps protocolOpen protocol for sitemap XML, sitemap indexes and loc elements.
How to use it
From public URL to verified release.
- 1Choose the release mission and declare whether the scope should be public.
- 2Keep the page open while respectful batches read public HTML and cross page signals.
- 3Export the evidence, deploy the fix, then load the project to verify the same scope.
Built for trust
Evidence without a false promise.
- No registration or paywall before your result.
- Only public URLs are fetched; HTML is not written into the project.
- Ready to ship describes the checked scope; it never guarantees indexing or ranking.
Frequently asked questions
What does Website Release Doctor check before launch?
It checks public HTTP access, redirects, robots directives, sitemaps, canonical tags, metadata, language alternatives, JSON-LD, sharing metadata, mixed content, links and initial HTML, then crosses page signals to find release-wide conflicts.
Does a Ready to ship result guarantee Google will index the site?
No. It means no technical blocker was detected inside the URLs and signals checked. Search engines decide what to crawl, index, canonicalize and rank, and production can still differ by network, user agent or later deployment.
Can I compare a website before and after a fix?
Yes. Download the SolveKit release project after the first check, deploy your fix, choose Verify fixes, load that local file and scan again. The comparison separates resolved, new and persistent findings.
Is the crawled website content stored?
No fetched HTML is written into the project. The downloadable file contains normalized signals, URLs, evidence and issues required for comparison; it excludes page HTML, cookies, credentials and form data.
Can I crawl 500 URLs without creating an account?
Yes. Select the 500-URL limit and keep the page open while the browser coordinates respectful batches. The target website or Cloudflare limits can still slow or stop a run, and the tool never bypasses access controls.
Keep solving
Related seo & marketing tools
Meta Tag Generator
Create a clean title, description, canonical, robots, Open Graph and viewport tag block, ready to paste.
SEO & MarketingOpen Graph Generator
Generate Open Graph tags for rich previews on social and messaging apps.
SEO & MarketingRobots.txt Generator
Create a practical robots.txt file with crawl rules and sitemap location.
SEO & MarketingUTM Campaign URL Builder
Add consistent UTM campaign parameters to any destination URL.
SEO & MarketingSERP Snippet Preview
Preview a page title, URL, and description as a search result.
SEO & MarketingWebsite Ad Revenue Calculator
Estimate daily, monthly, and annual website advertising revenue from page views and Page RPM.
SEO & Marketing