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 "related posts" block at the end of an article is where a reader decides to read on or leave, and default plugins fill it by shared tags, so a post on sourdough starter ends with a link to a Christmas cookie list. We read your posts and pick, for each one, the three to five that a reader would actually want next, with a short reason and a teaser line you can show in the block. You can paste the result into a manual related-posts field or use it to set up your plugin rules.
What is included
- What you getA related-posts table: for each post, three to five recommended next reads in order, with a one-line teaser for each and notes on posts that have no good match yet.
- Next readsThree to five picks per post, in order
- TeasersA one-line hook for each link
- Weak spotsPosts without a good match
- Plugin tipsRules for your related-posts setup
How it works
- 1PostsYou share the blog and post list
- 2ReadingWe read posts and pick next reads
- 3MapYou get the table with teasers
What we need from you
A link to the blog, the list of posts to cover (or the category to start with) and how the related block is set up now, by plugin, tags or manually.
We will ask you:
- Which posts or categories should the map cover?
- How is the related block set up now?
- Should some posts be promoted more often?
Compare packages
| Packages | BasicUp to 20 posts$10 | StandardUp to 50 posts$20 | PremiumUp to 120 posts$39 |
|---|---|---|---|
| Deadline | 2 days | 3 days | 5 days |
| Revisions | 1 | 2 | 2 |
| Posts mapped | up to 20 | up to 50 | up to 120 |
| Next reads per post | 3 | 3–4 | 4–5 |
| Teaser lines | 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
Can I keep my related-posts plugin?
Yes. Many plugins allow manual picks per post, and where they do not, the tips show how to tune their rules toward the map.
Is this different from an internal linking plan?
It covers only the end-of-post block, for readers who finished the article. Links inside the text are a separate service.
Do you count which posts get the most traffic?
We cannot see your analytics. If you paste your top posts, we give them more weight in the picks.