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
Canonical tags tell search engines which URL is the main version of a page, and hreflang tells them which page to show for each language or region; set wrongly, they cancel each other out, for example a German page pointing its canonical at the English one. We look at your page templates and URL patterns and write a rule for each: which canonical every template gets, how parameters, pagination and variants are handled, and the full hreflang set for each language version with return links and x-default. You get tag examples ready for your developer.
What is included
- What you getA canonical and hreflang plan by page template, with the rule, a correct tag example and the current problem for each, plus a list of specific URLs that break the rules today.
- Canonical per templateOne rule for each page type
- Parameters and pagesFilters, tracking, sorting and page 2
- hreflang setsEvery version, self-reference and x-default
- ConflictsCanonicals that cancel hreflang
- Broken URLsSpecific pages to fix now
How it works
- 1TemplatesYou list templates and versions
- 2RulesWe write a rule per template
- 3Hand-offYou get examples for developers
What we need from you
A link to the site, the page templates you have (home, category, product, article, filters), your language or country versions and their URL pattern, and examples of URLs with parameters.
We will ask you:
- Which page templates does the site have?
- Which language or country versions exist, and how are their URLs built?
- Paste a few URLs with parameters or duplicates you have noticed
Compare packages
| Packages | BasicUp to 4 templates$12 | StandardUp to 8 templates$25 | PremiumUp to 15 templates$45 |
|---|---|---|---|
| Deadline | 2 days | 3 days | 5 days |
| Revisions | 1 | 2 | 2 |
| Page templates | up to 4 | up to 8 | up to 15 |
| Language or region versions | up to 2 | up to 5 | up to 10 |
| Broken URL list | 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
Should a page's canonical point to itself?
Usually yes, for any page you want indexed. Pointing translations or page 2 at another URL is a common mistake the plan corrects.
Is canonical a command or a hint?
A strong hint. Search engines may pick another URL if signals disagree, which is why the plan aligns canonicals, links and sitemaps.
Will you change the tags in my theme?
No, we do not log in to your site. Your developer applies the rules from the plan.