Payment protectionDetails
- Revisions within the package are free.
- If you do not respond within 3 days of delivery, the work is accepted automatically.
The money is reserved when you pay and released only once you accept the work.
Example result
SEO audit: website of a regional plumbing company
Summary
| Area | Score | Main issue |
|---|---|---|
| Indexing and crawling | Needs work | 38 blog tags pages indexed, thin content |
| Technical health | Fair | Mobile load time 4.8 s on service pages |
| On-page | Needs work | 11 of 18 service pages share near-identical titles |
| Local signals | Weak | Town pages are copies with the town name swapped |
| Content | Fair | Blog traffic is high, but posts do not link to services |
Findings (excerpt)
1. Duplicate and weak titles (high priority)
11 service pages use the pattern "Plumbing Services | Northgate". Searchers and search engines cannot tell "boiler repair" from "drain unblocking".
| Page | Current title | Suggested title |
|---|---|---|
| /boiler-repair | Plumbing Services, Northgate | Boiler Repair in [City], Same-Day Callout, Northgate |
| /blocked-drains | Plumbing Services, Northgate | Blocked Drains Cleared in [City] from £89, Northgate |
2. Town pages are near duplicates (high priority)
The 7 town pages are 94% identical text. Each needs at least 250 words unique to that town: areas covered, typical jobs there, travel time, a local customer review.
3. Slow service pages on mobile (medium)
Hero images average 1.9 MB. Compressing to WebP and setting width to 1,200 px would bring load time to about 2.5 s.
4. Blog does not pass value to services (medium)
The top 10 posts get 62% of organic visits, but only 2 of them link to a service page. "Why is my boiler losing pressure?" alone gets about 1,100 visits a month and links nowhere.
5. Tag pages indexed (low)
38 /tag/ pages with 1–3 posts each. Set them to noindex.
Prioritised action plan
| # | Action | Effort | Impact | Who |
|---|---|---|---|---|
| 1 | Rewrite titles and meta descriptions for 18 service pages | 1 day | High | Content |
| 2 | Write unique content for 7 town pages | 3–4 days | High | Content |
| 3 | Add service links to the top 10 blog posts | 2 hours | Medium | Content |
| 4 | Compress hero images | 2 hours | Medium | Developer |
| 5 | Noindex tag pages, update sitemap | 1 hour | Low | Developer |
Re-check: crawl again 6 weeks after items 1–3 are live and compare impressions for "[service] + [town]" queries.
Client: Northgate Plumbing & Heating, 11 engineers, serving one city and 6 nearby towns Site: 214 pages: home, 18 service pages, 7 town pages, 160 blog posts, contact and legal pages Goal: more calls from local searches such as "boiler repair [town]"
The client and all details are made up.
About this service
The week before launch is when leftover placeholder text, a contact button pointing to the staging address, a broken password reset or a missing privacy page slip through, because the team has looked at the site too many times. We go through your new site as a first-time visitor and check every main path, link, form, text and page state against a launch checklist. You get a go or fix list by severity, so the team knows what must be done before launch and what can wait.
What is included
- What you getA pre-launch report with every problem found, grouped into must fix before launch, fix soon and nice to have, plus the checklist we used so your team can repeat it.
- Main pathsEach user path from start to finish
- Links and buttonsDead ends, staging links and wrong targets
- TextsPlaceholders, typos and inconsistent names
- Page states404, empty search, errors and thank-you pages
- BasicsLegal pages, contacts, favicon and page titles
How it works
- 1AccessYou send a link and the main paths
- 2Run-throughWe go through the site on the checklist
- 3Go or fixYou get problems sorted by severity
What we need from you
A link we can open without logging in (live or staging), the launch date, the main user paths such as buying or booking, and test accounts if a path needs sign-in.
We will ask you:
- When is the launch date?
- Which user paths must work on day one?
- Does any path need a test login?
- Which countries and languages is the site for?
Compare packages
| Packages | BasicSmall site$15 | StandardBusiness site$29 | PremiumStore or app site$55 |
|---|---|---|---|
| Deadline | 2 days | 3 days | 5 days |
| Revisions | 1 | 2 | 2 |
| Pages or screens checked | up to 15 | up to 40 | up to 80 |
| User paths tested | 1 | up to 3 | up to 6 |
| Reusable checklist | Yes | Yes | Yes |
| Order Basic | Order Standard | Order Premium |
Payment protection
You pay when you order, but the money is released only for accepted work.
- Fixed priceThe package price does not change after you pay.
- The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
- Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
- Free revisionsAsk for changes within your brief as many times as the package allows.
- Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
- Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
Questions and answers
Our staging site is password-protected. What then?
We need a link that opens in a browser. A temporary public preview link or simple shared access for a test user works; we never ask for admin or hosting access.
Is this an SEO pre-launch check?
No, this one is about visitors: paths, texts and pages that work. For search settings before launch, there is a separate pre-launch SEO checklist.
Do you test payments?
Only in test mode, if your shop has it switched on. We never make real payments.