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
A contact, booking or quote form is where a visitor finally decides to reach you, and small things stop them: a required phone field, a dropdown with forty options, an error message that wipes what was typed, or a vague "Submit" button with no word on what happens next. We fill in each of your forms with test data, check fields, labels, errors, the confirmation and the follow-up message, and rewrite the form so it asks only what you need.
What is included
- What you getA review of each form with the problems found and a rewritten version: field list, labels, error and button texts, and the confirmation message.
- Field auditWhich fields to cut, merge or make optional
- ErrorsMessages that say what to fix
- Button and promiseWhat happens next, in plain words
- After sendingThank-you page and confirmation text
How it works
- 1FormsYou send the pages with forms
- 2Test fillsWe test each form with dummy data
- 3RewriteYou get issues and new form texts
What we need from you
A link to the pages with the forms, what happens to a request after it is sent and which fields your team really needs to reply.
We will ask you:
- Which forms should we check?
- Which fields does your team actually use to reply?
- May we submit test requests, and how should we mark them?
Compare packages
| Packages | Basic1 form$10 | StandardUp to 3 forms$20 | PremiumUp to 6 forms$39 |
|---|---|---|---|
| Deadline | 1 day | 2 days | 4 days |
| Revisions | 1 | 2 | 2 |
| Forms reviewed | 1 | up to 3 | up to 6 |
| Rewritten form texts | Yes | Yes | Yes |
| Confirmation messages | 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
Will you send fake requests to my team?
Only if you allow it in the brief, clearly marked as tests. Otherwise we check everything up to the send button.
Do you check that the form email reaches us?
We cannot see your inbox. After a test submission you confirm whether it arrived, and we note it in the report.
Do you change the form on the site?
No, we do not log in to your site. You get the new field list and texts to set up in your form plugin or builder.