--- title: "Structured Data (Schema) In Nexter SEO" url: https://nexterwp.com/docs/structured-data-schema-overview/ date: 2026-07-17 modified: 2026-07-17 author: "Aditya Sharma" description: "Schema is the structured-data manager inside Nexter SEO. It builds the Schema.org JSON-LD that tells search engines exactly what each page is about, which is what powers rich results like..." word_count: 771 --- # Structured Data (Schema) In Nexter SEO Schema is the structured-data manager inside Nexter SEO. It builds the Schema.org JSON-LD that tells search engines exactly what each page is about, which is what powers rich results like review stars, FAQs, breadcrumbs, and product cards in search. Nexter → Content SEO → On-Page → Schema.   ### What Structured Data Is And Why It Matters Structured data is a machine-readable description of your content that lives in the page source as JSON-LD. A normal page tells Google "here is some text." Schema tells Google "this is an Article, written by this Person, published on this date, part of this WebSite, belonging to this Organization." Google reads that map and can then show your page as a rich result instead of a plain blue link. Concretely, well-formed schema helps you: - Qualify for rich results (review stars, FAQ dropdowns, breadcrumb trails, product price and availability, recipes, events). - Give search engines an unambiguous entity graph for your site (who publishes it, what the organization is, how pages relate). - Feed AI search and answer engines clean, structured facts they can cite. Nexter SEO writes this JSON-LD for you and keeps it bound to your live content through dynamic variables, so the output stays correct as posts are added and edited.   ### The Two Scopes: Site Wide vs Page Specific Schema entries are organized into two tables, and the split matters because it decides where each entry loads. **Site Wide Schema** describes your site as a whole and loads across the entire website. These entries answer "what is this website and who runs it." Shipped out of the box: - **WebSite** (WebSite / Entire Website) - **WebPage** (WebPage / Entire Website) - **Organization** (Organization / Entire Website) - **SearchAction** (Search Action / Entire Website) - **Person** (Person / Entire Website) **Page Specific Schema** describes an individual piece of content and loads only on matching pages. These entries answer "what is this particular page." Shipped out of the box: - **BreadcrumbList** (Breadcrumb List / All Singulars) - **Article** (Article / All Singulars, Exclude: All Products) - **Product** (Product / All Products) Notice how the defaults already avoid conflicts: Article loads on all singular pages but is excluded from products, while Product loads only on products. That is display conditions doing their job, covered in the conditions article linked below.   ## How To Manage Schema In Nexter SEO? Both tables use the same columns and controls, so once you learn one you know both. ![Adding and configuring a schema entry in Nexter SEO](https://nexterwp.com/wp-content/uploads/2026/07/nseo-05a-schema-add-configure.gif) - Each row shows **Schema Title**, **Schema Type**, **Condition**, and **Actions**. - Use **+ Add Schema** (top of the screen) to create a new entry. You pick a type, then fill the per-type field editor. - Use the row's **Edit** button (or the pencil icon) to open an existing entry and change its fields or variables. - **Duplicate** an entry when you want a near-identical variant, for example an Article schema tuned for a second post type. Copy it, then adjust the fields and conditions on the copy. - Use the **trash icon** to remove an entry you no longer need. - Click **Save** (top right) to write your changes. | Column | What it does | | ------ | ------------ | | Schema Title | The label for the entry as it appears in the table (for example "Article"). Internal only. | | Schema Type | The Schema.org type this entry outputs (for example Article, Product, Organization). | | Condition | Where the entry loads, for example Entire Website, All Singulars, or All Products. Set in the Display Conditions modal. | | Actions | Edit (open the field editor), pencil (edit), and trash (remove). |   #### Good To Know - Do not delete the default Site Wide entries unless you know you are replacing them. WebSite, Organization, and Person form the backbone entity graph that page-specific schemas reference through variables like `%schemas.organization%`. - Keep one entry per type and scope. Two Article entries both targeting all singulars will emit duplicate JSON-LD. - Schema output uses dynamic variables (the `%post.title%` style tokens), so an entry configured once stays accurate for every matching page automatically.   #### Troubleshooting - **Rich results not showing:** rich results are earned, not guaranteed. Confirm the JSON-LD is present with Google's Rich Results Test, then allow time for re-crawling. - **Two schemas fighting on the same page:** check display conditions. The default Article entry excludes All Products precisely so it does not collide with Product schema. Apply the same include/exclude discipline to custom entries. - **A field shows a raw token like `%post.title%` in output:** that means the variable did not resolve for that context (for example a term variable used on a singular). Swap it for a variable that exists on that page type. **Related:** [Add & Configure A Schema Entry](/docs/add-and-configure-a-schema-entry/) · [Supported Schema Types & Variables Reference](/docs/schema-types-and-variables-reference/) · [Schema Display Conditions](/docs/schema-display-conditions/)   [Explore Nexter Extension](https://nexterwp.com/nexter-extension/)   This is how you can manage structured data with Nexter SEO.