How to add schema markup to any website without a developer

What is schema markup?

Schema markup is a shared vocabulary, maintained at schema.org, for describing things on a web page in a form machines can read. Instead of a crawler guessing that a number is a price or that a name is the author, the markup says so directly.

There are three ways to write it: JSON-LD, Microdata and RDFa. Google supports all three and recommends JSON-LD, because it sits in one script block and does not need to be woven through your HTML. That also makes it the easiest format to add without touching your templates.

Structured data is not a ranking boost on its own. What it does is make a page eligible for rich results, such as review stars, product prices or breadcrumb trails, and help search engines understand the entities on the page. Google is clear that eligibility does not guarantee a rich result will be shown.

Which schema types matter most?

Schema.org lists hundreds of types, but most sites only need a handful. Pick the ones that describe what is actually on each page.

• Organization: your name, logo, website and official profiles. Put it on the homepage or about page so search engines connect your brand to its details.
• Article: headline, author, publish and update dates and images for blog posts and news. It helps Google show the right title, date and image for the piece.
• FAQPage: a list of questions with their answers, for pages that show those questions and answers visibly. Since 2023 Google shows FAQ rich results only for a limited set of well-known government and health sites, so for most sites it describes the page rather than earning a rich result.
• Product: name, image, price, availability and reviews for a product page. It can make a page eligible for product snippets with price and rating details.
• LocalBusiness: address, phone number, opening hours and location for a business with a physical place customers visit. Use the most specific subtype that fits, such as Restaurant or Dentist.
• BreadcrumbList: the page's position in your site's hierarchy, such as Home, Guides, then this guide. Google can use it to show a readable path in results instead of a raw URL.

How to add JSON-LD schema without a developer

JSON-LD is a block of text inside a script tag. Most website builders let you paste custom code into the head of a page or the whole site, which is all you need. Below is a minimal Organization example you can adapt.

1. Choose the schema type that matches the page, using the list above.
2. Write the JSON-LD. Start from Google's documentation for that type, which lists the required and recommended properties, or from the example below.
3. Fill in real values that match what visitors see on the page. Use full URLs for links and images.
4. Paste the script into the page's head using your CMS's custom code or header code setting. Site-wide types like Organization can go in the global header; page types like Article or Product belong on their own pages.
5. Publish, then test the live URL with the validators described in the next section.
6. Revisit the markup whenever the visible content changes, such as a new price, new hours or an updated article.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Bakery",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/logo.png",
  "sameAs": [
    "https://www.facebook.com/examplebakery",
    "https://www.instagram.com/examplebakery"
  ]
}
</script>

How to test and validate schema markup

Use two free tools, because they answer different questions.

Google's Rich Results Test checks whether a URL or code snippet is eligible for the rich results Google supports, and flags missing required properties. It renders the page, so it also picks up schema that is added by JavaScript. Use it for the types Google turns into rich results, such as Product, Article and BreadcrumbList.

The Schema Markup Validator at validator.schema.org checks any schema.org markup against the full vocabulary, including types Google does not use for rich results. Use it to catch typos, wrong property names and invalid nesting.

After launch, Google Search Console shows enhancement reports for detected rich result types, with errors and warnings across your whole site. Check them after any template change.

Common schema markup mistakes to avoid

• Marking up content that is not on the page. Google's guidelines require structured data to describe content visitors can see. Hidden or invented reviews can lead to a manual action.
• Using the wrong type. A service page marked up as a Product, or a blog post marked up as a LocalBusiness, confuses rather than clarifies.
• Leaving out required properties. A type missing its required fields is not eligible for its rich result.
• Copying markup between pages without editing it. Duplicated headlines, prices or dates tell search engines the wrong thing.
• Letting it go stale. Old prices, hours or availability in schema contradict the page and erode trust.
• Expecting a ranking jump. Schema helps search engines understand and display a page; it does not replace useful content.

Where SEOAmazing fits

When you add a site, SEOAmazing's crawler snapshots the structured data on each page along with titles, headings and other on-page elements. Its AI then proposes fixes, which can include JSON-LD schema, each with the current value, the proposed value, a severity and a one-line rationale. You can edit any proposal, and nothing changes until you approve it.

Approved schema is applied by the SEOAmazing pixel, a single script line in your site's head. Google renders JavaScript, so Googlebot can see it, and you can confirm that in the Rich Results Test. For AI crawlers that do not run JavaScript, SEOAmazing's prerender service can serve rendered HTML with the schema included; on your site that is set up with our help. Changes stay live while the snippet is installed.

Frequently asked questions