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
Moving to a new domain, platform or URL structure, or relaunching after a redesign, is the moment many sites lose half their search traffic, usually because old URLs return 404 or redirect to the home page. We build the SEO side of your move: a redirect map from each old URL to its best new match, a list of what must carry over (titles, content, internal links, structured data), and checks for before, during and after launch. You or your developer set up the redirects; the plan tells you exactly which ones and in what form.
What is included
- What you getA redirect map from old to new URLs with notes on unclear matches, a migration checklist for before, during and after launch, and in higher packages an 8-week monitoring plan.
- Redirect mapEach old URL to its best new match
- No home page dumpsReal matches or a reasoned fallback
- What must carry overTitles, content, links, markup
- Launch-day checksRedirects, indexing, sitemap, tracking
- MonitoringWhat to watch week by week
How it works
- 1URLsYou send old URLs and the new structure
- 2MapWe match URLs and write the checklist
- 3LaunchYour developer applies the redirects
What we need from you
A link to the current site, the list of old URLs (a crawl export, sitemap or pasted list), the new URL structure or new site address, the platforms involved and the launch date.
We will ask you:
- What exactly is changing?
- Can you provide the full list of old URLs?
- Which pages bring the most traffic or sales?
- When is the launch planned?
Compare packages
| Packages | BasicUp to 100 URLs$20 | StandardUp to 400 URLs$39 | PremiumUp to 1,000 URLs$75 |
|---|---|---|---|
| Deadline | 2 days | 3 days | 5 days |
| Revisions | 1 | 2 | 2 |
| URLs mapped | up to 100 | up to 400 | up to 1,000 |
| Migration checklist | Yes | Yes | Yes |
| 8-week monitoring plan | No | 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
Will we lose no traffic at all?
Some dip after a move is common even when everything is done right. A careful redirect map keeps it small and short, but no one can promise zero loss.
Should we migrate and redesign at the same time?
It is riskier, because it is harder to tell what caused a drop. If you must, the plan flags the pages where content changes most.
Do you set up the redirects?
No, we do not access servers or sites. The map is ready to hand to your developer or import into a redirect plugin.