What DIY schema markup actually involves

Doing schema markup yourself means writing JSON-LD code and adding it to your website's HTML, either directly or via your CMS. You do not need to be a developer, but you do need to:

  • Learn the JSON-LD format (curly brackets, quotes, commas in the right places)
  • Understand which schema.org types are relevant to your business
  • Know which fields matter most for AI visibility (not just what Google rewards)
  • Add the code to your website in a way that won't break anything
  • Validate the output using Google's Rich Results Test and Schema Markup Validator

None of this is technically difficult, but it takes 3–8 hours to research, write, and validate a solid initial implementation. If you have that time and a modest interest in the technical side of your website, DIY is entirely viable.

DIY is a good fit if you are...
Comfortable editing your website's code or CMS
Working to a tight budget and have time to invest
Happy to learn as you go and troubleshoot validation errors
Running a simple local business with standard schema needs

What plugin-based schema involves

WordPress plugins like Yoast, Rank Math, and Schema Pro generate schema markup automatically based on your page content and settings. They are fast to set up and require no coding. The limitations are:

  • Generic output — plugins generate standard schema, not the specific fields that matter most for AI visibility in your sector
  • Missing credential fields — hasCredential, areaServed, and sector-specific fields are rarely covered by generic plugins
  • Limited business type granularity — most plugins default to LocalBusiness or Organisation rather than the more specific types (Plumber, Dentist, HairSalon) that AI systems respond to

What done-for-you schema involves

A specialist implementation means someone who understands both schema syntax and AI visibility builds and deploys the markup for you. The difference from generic agency work is specificity — the markup is tailored to your exact business type, credentials, and the AI visibility goals you are trying to achieve.

Done-for-you is a good fit if you are...
Too busy to invest 6+ hours learning and implementing
In a sector with specialist schema needs (healthcare, legal, trades)
Wanting schema plus accompanying content changes as a package
Not confident you'll get it right and don't want to waste the time

The honest comparison

DIY

Cost: Free to £99 for tools.
Time: 4–8 hours initial, plus ongoing updates.
Risk: Errors that reduce effectiveness. Not dangerous, just wasteful.
Ceiling: Limited by your knowledge of what to include.

Plugin

Cost: £0–£99/year.
Time: 30–60 minutes setup.
Risk: Generic output misses the highest-value fields.
Ceiling: Suitable for basic visibility, not sector-specific optimisation.

Done-for-you

Cost: £200–£800 for a full implementation.
Time: 1–2 hours of your input to brief the work.
Risk: Choosing a generalist who doesn't understand AI visibility specifically.
Ceiling: Limited only by the quality of the specialist.

Questions about DIY vs done-for-you schema

Can I do schema markup myself without technical knowledge?
+
You can learn to write JSON-LD schema markup without being a developer. The syntax is relatively straightforward and Google's tools help you validate it. The challenge is knowing which schema types matter most for your business, which fields are most effective for AI visibility, and avoiding the common errors that result in markup that validates but doesn't perform.
What are the risks of DIY schema markup?
+
The main risks are: incorrect syntax that fails validation, using generic types when more specific ones are available, missing the most impactful fields for your business type, and schema that is inconsistent with the content on the page. None of these are catastrophic — schema errors won't harm your site — but they result in markup that doesn't improve your AI visibility.
When does done-for-you schema make sense?
+
Done-for-you schema makes sense when: your time is worth more than the cost of the service, you want confidence that it's done correctly, you need specialist schema types for your industry rather than generic LocalBusiness, or you want schema plus the accompanying content changes that maximise its effectiveness.