What Article schema is
Article schema is the Schema.org type used to describe news articles, blog posts, editorial guides, and long-form content. It sits inside the @context https://schema.org graph as @type Article (or its subtypes BlogPosting, NewsArticle, Report, ScholarlyArticle). The shape: a JSON object naming the page's headline, the author Person entity, the publisher Organization, the dates of publication and last modification, and a representative image. Google's canonical structured-data documentation names Article as the type to use for editorial pages, with BlogPosting as the subtype preferred for blog posts and NewsArticle reserved for time-sensitive journalism.
When to use Article schema (and when not to)
Use Article (or BlogPosting) on every editorial page on your Squarespace site: blog posts, long-form guides, case studies that read as narrative, opinion pieces. Do not use it on service pages, product pages, the homepage, or contact pages — those have their own schema types (Service, Product, Organization). The honest test: would a reader call this page 'an article'? If yes, install Article. If no, install something else.
Rich-results status in 2026
Article structured data is active in 2026. It does not always produce a visible rich-result enhancement — Google's canonical guidance is that Article markup helps Google understand the page (better title text, image, date) but does not guarantee a SERP enhancement. The bigger 2026 win is AI engine citation: ChatGPT, Perplexity, Claude, and Gemini parse Article schema as a fast path to attribution, materially raising the odds the page is cited as a source.
Required and recommended fields
Google's canonical Article documentation lists zero required properties. The recommended set — the fields that meaningfully affect how Google understands the page and how AI engines attribute citations — is five long: headline (the page title), author (a Person object with name and url), publisher (an Organization with name and url), datePublished (ISO 8601 date), dateModified (ISO 8601 date), and image (a URL or ImageObject). On Squarespace, every Article should also reference the page URL as mainEntityOfPage.
Copy-paste JSON-LD example
The block below is a complete Article schema for a Squarespace blog post on a coastal interior design studio. Replace the headline, author, publisher, dates, and URL with your real values. The example uses BlogPosting (the subtype) because that aligns with what Squarespace auto-emits on blog templates.
Where to paste it on Squarespace
Open the blog post in the Squarespace editor. Click the gear icon to open Page Settings. Open the Advanced tab. Find the Page Header Code Injection field. Paste the entire script block (including the wrapping script tags) into the field. Save. Code Injection is available on Core, Plus, Advanced, Business, Commerce Basic, and Commerce Advanced plans — not Personal. If you are on Personal, the workaround is a plan upgrade. There is no native way to inject JSON-LD on Personal-tier Squarespace.
Validation steps
Run the live page URL through Google's Rich Results Test at search.google.com/test/rich-results. Confirm the Article type is detected and zero errors are reported. Warnings about optional fields (missing logo, no aggregateRating) are fine. Errors are not. The most common error is malformed JSON — usually a smart quote that snuck in through Squarespace's auto-correcting editor. Re-paste from a plain text editor (VS Code, TextEdit set to plain text) to fix.
Common gotchas on Squarespace
Three gotchas catch most first-time Article installs on Squarespace. First: duplicate emission. Squarespace blog templates auto-emit a BlogPosting block already; layering a second one on top produces two BlogPosting entities for the same page. Fix by viewing source first and either extending the auto-emitted block via @graph or replacing it. Second: smart quotes. Squarespace's editor auto-corrects straight quotes to curly quotes, breaking JSON syntax. Fix by authoring in a plain text editor. Third: stale dateModified. Owners often forget to bump dateModified on real edits, which under-signals freshness to Google and AI engines.
Related schema types
Article never ships alone. The entities Article references — Person (author) and Organization (publisher) — need their own schema blocks. The page Article describes typically sits inside a navigation tree, so BreadcrumbList belongs alongside. If the article carries a step-by-step section that genuinely qualifies as a how-to, HowTo schema layers on top (knowing it no longer triggers a Google rich result, but still helps AI extraction).