WordPress AI Readiness Checklist — CBOUND Observatory 005 (Revised)
CBOUND Observatory · Publication 005

The WordPress AI Readiness Checklist

A field-by-field checklist for making a WordPress site easier for machines to access, interpret and connect to a clearly identified person, organisation or service — without claiming rankings, AI citations or recommendations.

📅 Revised September 2026📖 12-point checklist🔗 cbound.mu
01 — The problem

A complete WordPress site can still publish very little machine-readable business information

A WordPress website can look complete to a visitor while publishing surprisingly little structured information about the person, organisation, services or location behind it. Titles, descriptions, contact details and visible page copy may all be present, yet the relationships between those pieces of information can remain implicit.

This checklist focuses on the website-controlled signals that can make public information easier for search engines, AI-enabled systems and other machines to access and interpret: organisation identity, structured data, services, contact information, linked identities, crawlability and technical accessibility.

CBOUND definition

AI readiness is used here to describe website-controlled conditions that make public information easier for machines to access, interpret and connect. It is a readiness check, not an AI visibility score. It does not determine whether an AI system will cite, rank or recommend a website.

The boundary

CBOUND can test what a website publishes, validate what is machine-readable and observe later search changes. It cannot promise rankings, citations, recommendations, Knowledge Panels or inclusion in any external AI answer.

02 — Before you start

Standard WordPress vs machine-ready WordPress: what actually changes

The practical difference is not a redesign. It is the addition of clearer identity, structured publishing, consistent business information and validation. Most of these changes can be made within an existing WordPress setup.

Signal Standard WordPress Machine-Ready WordPress
Site identity Site title + tagline only Person or Organisation schema with name, type, and description
About page Written for humans, no structured data JSON-LD Person block with trade, location, and sameAs links
Contact page Phone number and email in plain text LocalBusiness schema with address, telephone, and opening hours
Social links Icons in footer linking to profiles sameAs array in JSON-LD connecting all platform identities
Services Text list or cards on a services page Service schema with name, description, and areaServed
Yoast / RankMath Green light on title and meta description Site representation set, social profiles connected, schema type selected per page
Validation Not checked Tested in Google Rich Results Test after every change
03 — Yoast SEO

Five Yoast settings that make business information more explicit

Yoast SEO can output useful schema, but the value comes from configuring the site’s identity and page context accurately. The settings below help make important information explicit and machine-readable; they do not determine how any external AI system will rank or recommend the site.

Yoast SEO Site Representation settings panel

Figure 01 — Yoast SEO Site Representation panel. Organisation/Person settings and linked public profiles help make site identity more explicit.

  • □
    Set Site Representation to Person or Organisation Yoast SEO → General → Site Representation. Choose Person for sole traders and freelancers. Choose Organisation for businesses. This single setting changes the root schema type that Yoast outputs on every page.
    PLUGIN
  • □
    Add your name and description If set to Person: add your full name and a specific professional description — not “consultant” but “licensed electrician based in Quatre Bornes, Mauritius, specialising in residential wiring and solar installation since 2015.”
    PLUGIN
  • □
    Connect all social profiles Add public profiles that genuinely represent the same person or organisation. These may be expressed through sameAs so machines can connect equivalent public references.
    PLUGIN
  • □
    Set schema type on your About and Services pages Use the most accurate supported page/schema type for the visible content. The goal is to describe what the page is, not to force a search result.
    PLUGIN
  • □
    Enable breadcrumbs Breadcrumb markup can describe a page’s position within the site structure and make those relationships explicit to supported parsers.
    PLUGIN
04 — RankMath

RankMath schema: the settings panel that most users walk past

RankMath offers granular schema controls for content types and individual pages. The important task is to choose types and properties that accurately describe visible content, then validate the markup.

RankMath schema markup guide showing before and after rich results

Figure 02 — Example of a standard search result and a richer presentation. Structured data can support eligible search features, but it does not guarantee that Google will display them.

  • □
    Enable the Schema module RankMath → Dashboard → Modules → Schema. Toggle it on. Without this, RankMath outputs no structured data regardless of other settings.
    PLUGIN
  • □
    Set default schema type per post type RankMath → Titles & Meta → Posts / Pages. For each content type, set the default schema. Blog posts → Article. Service pages → Service. About page → Person or LocalBusiness. Product pages → Product.
    PLUGIN
  • □
    Add LocalBusiness schema to your homepage or contact page Use LocalBusiness only when it accurately represents the business shown on the page. Include factual fields such as name, address, telephone and opening hours where applicable. This describes the business; it does not guarantee a local panel or AI answer.
    PLUGIN
  • □
    Add FAQ schema to key pages (RankMath Pro) Use FAQ content where genuine questions are useful to visitors. Add structured markup only when it accurately represents visible content and follows current platform guidance; do not treat it as a guarantee of AI or rich-result exposure.
    PRO
05 — JSON-LD

The manual JSON-LD block: what to write and exactly where to paste it

JSON-LD is a structured-data format commonly used to describe information in machine-readable form. It can express entities, relationships and factual properties without changing the visible design of the page.

You do not need to be a developer to add it. The three methods below are ordered from simplest to most technical:

1

Insert Headers and Footers plugin (recommended for non-developers)

Install the free “Insert Headers and Footers” plugin by WPBeginner. Go to Settings → Insert Headers and Footers → Scripts in Header. Paste your JSON-LD block there. It will appear on every page of your site.

2

Yoast or RankMath custom schema field

Both plugins allow you to paste raw JSON-LD into a custom schema field on individual pages. This is the cleanest method if you want page-specific schema — for example, a Person block on your About page and a LocalBusiness block on your Contact page.

3

Direct theme header (for developers)

Add the block directly to your theme’s header.php file, immediately before the closing </head> tag. Use a child theme to avoid losing the change on theme updates.

Here is a complete Person JSON-LD block for a sole trader or freelancer. Replace the values with your own details:

<script type=“application/ld+json”> { “@context”: “https://schema.org”, “@type”: “Person”, “name”: “Marie Fontaine”, “jobTitle”: “Electrician”, “description”: “Licensed electrician based in Quatre Bornes, Mauritius, specialising in residential wiring, solar panel installation, and electrical fault diagnosis since 2018.”, “address”: { “@type”: “PostalAddress”, “streetAddress”: “12 Rue des Flamboyants”, “addressLocality”: “Quatre Bornes”, “addressCountry”: “MU” }, “telephone”: “+230 5700 0000”, “url”: “https://yoursite.mu”, “sameAs”: [ “https://linkedin.com/in/marie-fontaine-mu”, “https://directories.mu/listing/marie-fontaine-electrician”, “https://jobpost.mu/aivisibility/marie-fontaine” ] } </script>
Common mistake

The sameAs property can connect a person or organisation on your website with other public URLs representing that same entity. Use only accurate references. Consistent public information reduces ambiguity; it does not create a measurable universal AI confidence score.

06 — The full checklist

12-point WordPress AI Readiness Checklist

Work through these in order. The objective is to make public information explicit, technically accessible and internally consistent. Validate each change, then observe what happens rather than assuming an external outcome.

  • □
    1. Set Site Representation in Yoast or RankMath Person or Organisation — the root schema type for your entire site. 5 minutes.
    PLUGIN
  • □
    2. Write a specific, entity-rich description Trade + location + years of experience + specialisation. Not “consultant” — “solar installation contractor based in Mahebourg, Mauritius, since 2016.” 15 minutes.
    FREE
  • □
    3. Connect all social and directory profiles in sameAs Link only public profiles that genuinely represent the same entity. Consistency helps reduce ambiguity across public references. 20 minutes.
    PLUGIN
  • □
    4. Add LocalBusiness or Person JSON-LD to your homepage Use the Insert Headers and Footers plugin or RankMath’s custom schema field. Include name, address, telephone, and sameAs. 30 minutes.
    CODE
  • □
    5. Set page-level schema types on key pages About page → AboutPage. Services → Service. Contact → ContactPage. Blog posts → Article. 20 minutes.
    PLUGIN
  • □
    6. Validate with Google Rich Results Test Test your homepage and About page at search.google.com/test/rich-results. Fix any errors before proceeding. 15 minutes.
    FREE
  • □
    7. Add Service schema to each service page Include: name, description, areaServed (Mauritius or specific district), and provider (linking back to your Person or Organisation entity). 30 minutes.
    CODE
  • □
    8. Add FAQ schema to your top 3 pages Write 3–5 genuine questions and answers where they help visitors. Mark up only visible, accurate FAQ content when appropriate. Do not assume inclusion in AI answers. 45 minutes.
    PLUGIN
  • □
    9. Create or claim your Google Business Profile For eligible local businesses, keep the public business name, category, location and website details accurate and consistent. Treat it as a public business record, not a guarantee of search or AI placement. 1 hour.
    FREE
  • □
    10. Submit your sitemap to Google Search Console Submit the sitemap so Google can discover eligible URLs more efficiently and use Search Console to inspect crawl/indexing issues. Submission does not guarantee indexing. 20 minutes.
    FREE
  • □
    11. Create an AI Visibility Profile on JobPost.mu A JobPost.mu profile can provide another public URL where professional information is presented in a structured, consistent format and linked back to the person’s own website. It does not guarantee visibility or citation by external AI systems.
    FREE
  • □
    12. Re-validate and re-submit after every significant change When services, location or contact details change, update visible content and structured data together, then re-validate. The objective is consistency between what people see and what machines can parse. 15 minutes per update.
    FREE
07 — Validation

How to confirm that your structured data is valid

Writing structured data is only half the work. Validation checks whether the markup is syntactically valid and whether supported properties are recognised. Validation is not a prediction of rankings, Knowledge Panels or AI citations.

Google Rich Results Test tool interface

Figure 03 — Google Rich Results Test. Use it to validate supported structured-data implementations and identify errors or warnings. Eligibility does not guarantee display.

Google Rich Results Test (search.google.com/test/rich-results) — tests a specific URL and shows which rich result types are eligible. Use this after every schema change. It catches syntax errors, missing required fields, and unsupported schema types.

Google Search Console → Enhancements — once your site is indexed, Search Console shows a report for each schema type it has found. This is where you see real-world errors across all pages, not just the ones you manually test. Check it monthly.

What validation can tell you

The Rich Results Test can identify supported structured-data types, errors and warnings for the tested URL. Search Console can later show indexing and enhancement information where available. These tools do not determine Knowledge Panel eligibility, measure ChatGPT visibility or prove that an AI system has “resolved” an entity.

08 — The structured profile layer

Why an additional structured public profile can improve consistency

Your WordPress site can remain the primary public source for your business or professional identity. Additional public profiles can be useful when they present the same factual information consistently and link back to the primary website.

A JobPost.mu profile provides another public URL where professional information can be presented in a structured format and linked to the person’s own website and other public profiles. The value is consistency and explicit structure — not an invisible confidence score or guaranteed recommendation by an external system.

JobPost.mu AI Visibility Guide showing the scoring system and GEO vs SEO comparison

Figure 04 — JobPost.mu structured profile guide. The relevant principle here is consistent, explicit public information across connected URLs.

The profile is free to create and takes approximately 10 minutes. Where a downloadable JSON-LD file is provided, review it for accuracy before embedding it in WordPress so the structured data matches the visible profile and website information.

09 — What to expect

What changes can actually be observed?

There is no reliable fixed timetable from publishing structured data to a ranking, Knowledge Panel, AI citation or recommendation. Crawl and indexing times vary, and external systems make their own decisions. The useful approach is to separate what you can validate immediately from what can only be observed later.

StageWhat you can verify
ImmediatelySchema is present, markup validates, pages are reachable, sitemap and robots directives are correct, canonical URLs are set, and public business information is consistent.
After crawling / indexingSearch Console may provide evidence of discovered or indexed pages, queries, impressions, clicks and technical issues. Timing varies and indexing is not guaranteed by submission alone.
Over timeRecord whether query diversity, non-branded impressions, page exposure or other observable search signals change. Do not automatically attribute a change to schema or any single intervention.
CBOUND observation model

Website → Is the information present?
Structure → Is it machine-readable?
Search → Is the site being discovered or tested against queries?
Outcome → Did observable exposure change?

What this checklist cannot guarantee

Ranking, citation, recommendation, AI selection, Knowledge Panel appearance, rich-result display or inclusion in a particular AI answer. External outcomes may be observed separately when evidence exists, but they are not guaranteed consequences of completing this checklist.

Record a baseline before making changes

For a simple before-and-after observation, record indexed pages, branded impressions, non-branded impressions, number of queries, leading pages, crawl/indexing issues and structured-data validation status. Then use the same measures later.

Measurement loop

IMPLEMENT → VALIDATE → WAIT FOR CRAWLING → OBSERVE → COMPARE

Research note

What CBOUND means by readiness

This publication evaluates website-controlled conditions. It distinguishes between what can be tested directly, what can be observed later, what may be inferred cautiously, and what cannot be known from the website alone.

Publication principle

Make the website explicit. Validate what you control. Observe what happens next. Do not promise what external systems will do.