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
An HTML sitemap is a regular page for visitors that lists your sections and key pages, useful on large sites, in government and university sites, for accessibility and as a safety net when the menu hides deep pages. Most auto-generated ones are a flat wall of links. We group your pages into clear sections with headings, decide which pages belong there and which do not, and write the page as ready HTML or a structured list you can build in your CMS.
What is included
- What you getAn HTML sitemap page: grouped sections with headings and short intros, the list of links with clear names, ready as HTML or a structured list, and rules for keeping it updated.
- GroupingPages sorted into clear sections
- What belongsKey pages in, utility pages out
- Link namesReadable titles instead of URLs
- Ready markupHTML with headings and lists
How it works
- 1SourceYou point to the sitemap or menu
- 2StructureWe group and name the pages
- 3PageYou get HTML ready to publish
What we need from you
A link to the site, your XML sitemap or menu as the source of pages, the sections that matter most and pages that must stay out, such as thank-you or test pages.
We will ask you:
- Where should we take the page list from?
- Which sections matter most to visitors?
- Which pages should not be listed?
- Should the result be HTML or a list for your page builder?
Compare packages
| Packages | BasicUp to 60 pages$10 | StandardUp to 200 pages$20 | PremiumUp to 500 pages$39 |
|---|---|---|---|
| Deadline | 1 day | 2 days | 4 days |
| Revisions | 1 | 2 | 2 |
| Pages listed | up to 60 | up to 200 | up to 500 |
| Sections | up to 6 | up to 12 | up to 25 |
| Ready HTML | 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
Is an HTML sitemap still useful for SEO?
It is mainly for visitors. It also gives deep pages one more internal link, which helps on large sites, but it does not replace an XML sitemap.
Should it list every page?
No. On big sites it lists sections and key pages, not thousands of products or posts. We set the cut-off with you.
Will it stay up to date by itself?
A handmade page does not. The rules show how to update it, or how to set a plugin to build the same structure.