Schema Markup Pre-Launch Checklist for New Sites
Launching a new website is exciting, but if you skip structured data checks, you could be leaving search engines guessing about your content. Schema markup (structured data) helps search engines understand your pages, but only if it is implemented correctly. This pre-launch checklist walks you through the essential checks to ensure your schema markup is ready before you go live.
Why schema markup matters before launch
Structured data gives search engines explicit clues about your content — what a page is about, who wrote it, what products you sell, and more. It does not guarantee rich results (Google has tightened eligibility, and many rich result types are now limited or discontinued), but it does help search engines parse and classify your pages accurately. Fixing schema issues before launch is far easier than debugging them after indexing.
Pre-launch schema checklist
1. Choose the right schema types for your pages
Not every page needs the same markup. Map your page types to appropriate schema:
- Homepage: Organization or LocalBusiness (if you have a physical location).
- Blog posts / articles: Article or BlogPosting.
- Product pages: Product with Offer and AggregateRating (only if you have genuine reviews).
- Contact page: ContactPage.
- FAQ sections: FAQPage — but note that FAQ rich results are now limited to authoritative government and health sites. The schema still helps search engines understand your content, but do not expect a dropdown in search results.
- How-to content: HowTo schema — Google has discontinued HowTo rich results entirely. You can still use it for semantic clarity, but it will not produce a visual rich result.
Avoid marking up content that does not exist on the page. Schema must reflect visible content.
2. Use JSON-LD format
Google recommends JSON-LD (JavaScript Object Notation for Linked Data) because it is easy to implement and maintain. Place it in the <head> or <body> of your page, wrapped in <script type="application/ld+json">. Avoid mixing formats (Microdata, RDFa) unless you have a specific reason.
3. Validate with the right tools
Before launch, run every page through:
- Google's Rich Results Test (search.google.com/test/rich-results) — shows which rich result types your page is eligible for and flags errors.
- Schema Markup Validator (validator.schema.org) — checks your markup against Schema.org vocabulary.
Do not use Google's Structured Data Testing Tool or Structured Data Markup Helper — both are retired. Stick to the current tools above.
4. Check for required and recommended properties
Each schema type has required properties. For example:
- Article: headline, image, datePublished, author.
- Product: name, image, offers (with price, priceCurrency, availability).
- LocalBusiness: name, address, telephone.
Missing required properties can invalidate your markup. Recommended properties (like description, sameAs) improve clarity but are not mandatory.
5. Ensure URLs and IDs are correct
Use absolute URLs (https://example.com/page) in your schema, not relative paths. If you reference an @id (a unique identifier for an entity), make sure it is consistent across your site. Broken or mismatched IDs can confuse search engines.
6. Avoid common pitfalls
- Marking up hidden content: Schema must describe visible content. Do not mark up text that is hidden from users.
- Duplicate or conflicting markup: Multiple schema blocks for the same entity can cause conflicts. Consolidate where possible.
- Fake reviews or ratings: Never mark up reviews you do not have. This violates Google's guidelines and can lead to manual actions.
- Over-marking: Do not add schema for the sake of it. Only mark up what is relevant and accurate.
7. Test on staging before launch
If you have a staging environment, test your schema there first. Use the Rich Results Test on staging URLs to catch issues before they go live. If staging is not available, test on a few live pages immediately after launch and fix any errors.
8. Monitor after launch
Once live, use Google Search Console's Enhancements reports to monitor schema errors and warnings. Address issues promptly. Also, check the URL Inspection tool to see how Google interprets your structured data.
Final checks before you hit publish
- Every key page has appropriate schema markup.
- JSON-LD is used and validates without errors.
- Required properties are present and accurate.
- No hidden or fake content is marked up.
- URLs are absolute and consistent.
- Staging tests passed (or live tests are scheduled).
Structured data is not a magic bullet, but it is a foundational part of a technically sound website. A few minutes of validation before launch can save hours of troubleshooting later.
Ready to see how your site's structured data stacks up? Run a free website audit to get a full report on schema, SEO, speed, and more — with prioritized fixes you can act on immediately.
For more guides on technical SEO and site health, visit our guides library.
More guides · Compare audit tools · Run a free website audit