SEOPayment 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
With every language you add, a site gets a new set of ways to go wrong in search: hreflang tags that point to missing pages or have no return link, the wrong language codes, canonicals that send every version to the English one, redirects by visitor location that stop search engines from ever seeing the other versions, and pages where only the menu is translated. We audit all language versions together: structure by folders, subdomains or country domains, hreflang and x-default, canonicals, sitemaps, translated titles and descriptions, untranslated and mixed-language pages, and the usual technical checks. Pages are counted across all languages. You get a report and a plan by priority. We do not translate or proofread texts, edit the site or promise positions.
What is included
- What you getA report on the SEO problems found across your language versions, covering as many pages as your package has in all languages together, and a plan ordered by priority with corrected examples of tags where needed. You get it on the order page to read or download.
- HreflangCodes, return links and x-default
- Site structureFolders, subdomains or country domains
- Redirects by locationVisitors and search engines can reach every version
- Untranslated pagesMixed languages and copied titles
- Canonicals and sitemapsEach version points to itself
How it works
- 1BriefYou send the link and the list of versions
- 2AuditWe go through every language version
- 3Report and planYou get findings and a plan by priority
- 4RevisionsYou ask questions or for more detail within your package
What we need from you
A link to the site, the list of languages and countries with their addresses, which version is the main one, how visitors are sent to a version (a language switcher or a redirect by location), and which language versions matter most for your business.
We will ask you:
- Which site should be audited?
- Which languages and countries does it have?
- How do visitors reach their version?
- Who will make the changes?
Compare packages
| Packages | BasicUp to 50 pages, all languages$35 | StandardUp to 500 pages, all languages$69 | PremiumUp to 5,000 pages, all languages$132 |
|---|---|---|---|
| Deadline | 2 days | 3 days | 5 days |
| Revisions | 1 | 2 | 2 |
| Site type | Multilingual site | Multilingual site | Multilingual site |
| 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
How are pages counted on a multilingual site?
Every language version of a page counts as a page. A 100-page site in five languages is 500 pages, so it fits the Standard package.
Do you check the quality of the translations?
We flag pages left untranslated, mixed languages and titles copied from another version. Proofreading the translations is not part of the audit.
Should we redirect visitors to their language by location?
A forced redirect can hide versions from search engines. The plan explains what to do on your site, for example offering the version instead of forcing it.
Do you need logins to my site or analytics?
No. The audit works from the public pages of the site, so a link is enough. If you have figures from Google Search Console or analytics, describe them in the brief and we take them into account.
Will you make the changes on the site?
No, we do not access sites. The audit is a report with a plan; you or your developer make the changes by following it step by step.
Did not find your answer?


