ShipworkSite inspection
Striking distance

Crawlability

PaginationAre paginated pages set up right?Internal searchIs site search eating crawl budget?URL parametersAre parameters creating duplicates?Log analyserWhat does Googlebot actually crawl?Robots builderNeed a robots.txt file?Soft 404sAre pages “not found” but returning 200?JavaScriptCan crawlers see it without running JS?FreshnessIs my site quietly going stale?Robots.txtDoes robots.txt say what I think?

Indexing

Sitemap lastmodAre my sitemap dates valid?SitemapIs my sitemap actually fetchable?IndexingIs Google allowed to index my pages?CanonicalsIs Google indexing the wrong URL?Index signalsDo sitemap and index signals agree?Redirect builderNeed the redirect rules?RedirectsAre my URLs answering directly, over HTTPS?

On-page

Keyword ideasWhat are people searching for?SERP previewHow does my page look in Google?Content qualityAre your pages too thin or too alike?Image weightAre images slowing the page?CannibalizationAre pages competing with each other?On-page checkDoes the page use its target phrase?ImagesAre my images accessible and loading?DuplicatesDo my pages compete for one query?

Links

Orphan pagesWhich pages can no link reach?Link graphHow deep do your pages sit?Anchor textDo links say what they point at?Outbound linksAre external links still alive?Broken linksAre internal links sending visitors nowhere?

Structured data

Rich resultsIs my markup eligible for a rich result?Structured dataIs my product schema valid?Schema coverageDo my key pages carry structured data?Social previewHow does my page look when shared?Schema vs pageDoes markup match the page price?Schema builderNeed valid JSON-LD?

International

Hreflang sitemapDo page and sitemap hreflang agree?HreflangDo my language versions link back?Hreflang builderNeed the hreflang tags?
Every error, explainedGuides →
Pricing Learn Guides
Sign in

Signing in is optional: it keeps your account, watches and connections on any device. Every free check, the audit and the score work with no account at all.

Sign in with GoogleOpens your account, or creates a free one PricingPlans and credit packs for the paid jobs

Which queries are one push away from page one?

Most checks start from something broken. This one starts from something already profitable: the queries you appear for that are just past page one, where real impressions prove demand and a modest improvement can move them up. The work is to move an existing page, not to invent a topic.

Reads the search property you have connected, with read-only access, over the last 28 days. Nothing is stored.

What this check inspects

When a search property is connected with read-only access, Shipwork reads the queries and the pages they rank for over the last 28 days, then keeps the queries sitting just past page one: an average position above 10 and at or below 20. Each query is attributed to the URL that actually carries it, and when one query ranks on more than one page the row with the most impressions wins, so the work list names the page to improve rather than the phrase alone. The list is ranked by impressions and the top five are spelled out. It also compares the run against a saved snapshot of the previous run and reports any query that lost ground: an average position that slid by three or more, or clicks that fell by a fifth with at least two clicks lost.

What a failure means

This check reads your own search data, so with no property connected it says so plainly and produces no list rather than guessing. A property with no query impressions in 28 days is itself the finding. A query inside the band is a warning, because it has proved demand through real impressions and only needs to move. A query flagged as decayed is the one to rework first, since it was in reach and is heading the wrong way. On a healthy site there is no error state here: a site whose queries all sit on page one or far down gets an informational note, not a failure.

How to fix it

  1. Work the highest-impression query in the band first. It is the largest prize the page already qualifies for.
  2. Improve the exact page the query is attributed to, rather than writing a new one.
  3. Treat a decay line as urgent: a query that slid three positions or lost a fifth of its clicks is moving away from page one.
  4. Re-run after the change. Each run is saved as a baseline, so the next one shows whether the query moved.

A typical failure, worked through

The setupA store connects its search property. Over 28 days a collection page keeps appearing for "waterproof hiking boots" at position 13, with tens of thousands of impressions and a handful of clicks, while another query has slipped from position 6 to 9.

What the check reportsThe check lists the query against that exact page at position 13, with its impressions and clicks, and adds a decay line naming the query that fell from 6 to 9 since the last run.

The pointThe demand is already proven by the impressions, so the work is to move an existing page rather than to find a new topic. That is why this is a rework list, and why it is worth more than a list of errors.

Questions

Do I need to connect anything?
Yes. The check reads your own search data, so it needs read-only access to the search property for the site you are checking. Without a connection it says so and gives no list.
What does just off page one mean?
An average position above 10, so below the first ten results, and at or above 20. Past 20 the work usually takes months, so the band stays narrow enough to be a work list.
Why 28 days?
It is the reporting window the search data uses, so this check and the Search Console check read the same period.
Is a better position promised?
No. Position is an average across every search the page appeared in, and it moves. The check reports what happened, not a forecast.

Related checks and guides