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
Recipe results with a photo, rating and cooking time win most of the clicks for food queries, and they depend on complete Recipe markup: ingredients, step-by-step instructions, times in the right format, yield, nutrition and video if you have one. Recipe card plugins usually handle the basics but leave out steps, keywords or cuisine, or break when a post has two recipes. You paste your recipes or send the post links, and we write full Recipe JSON-LD for each, with HowToStep instructions and the fields Google recommends.
What is included
- What you getComplete Recipe JSON-LD for each recipe with ingredients, timed steps, yield, cuisine, keywords and nutrition where given, plus a field checklist for your recipe card plugin.
- Steps as stepsHowToStep instructions, not one text blob
- Times and yieldPrep, cook and total time in ISO format
- Recommended fieldsCuisine, category, keywords, video
- Plugin checklistFields to fill in WP Recipe Maker or Tasty
How it works
- 1RecipesYou paste recipes or post links
- 2MarkupWe write full Recipe JSON-LD
- 3TestYou paste and test in Google's tool
What we need from you
Your recipes pasted as text (ingredients, steps, times, servings) or links to the posts, the photo URLs, your recipe card plugin and any nutrition data you already have.
We will ask you:
- Which recipes should be marked up?
- Which recipe card plugin do you use, if any?
- Do you have nutrition data or recipe videos?
Compare packages
| Packages | BasicUp to 5 recipes$10 | StandardUp to 15 recipes$20 | PremiumUp to 35 recipes$39 |
|---|---|---|---|
| Deadline | 2 days | 3 days | 5 days |
| Revisions | 1 | 2 | 2 |
| Recipes | up to 5 | up to 15 | up to 35 |
| Step-by-step instructions | Yes | Yes | Yes |
| Plugin field checklist | 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
My plugin already adds recipe markup. Do I need this?
Maybe not for every post. We check what the plugin outputs and either give you fields to fill in or full JSON-LD where the plugin falls short.
Do you calculate calories?
No. We add the nutrition data you provide; we do not calculate it.
Can I add star ratings myself?
Only real ratings from readers that are shown on the page can go into the markup. We never add made-up ratings.