. Save."},{"@type":"HowToStep","position":5,"name":"Validate in the Rich Results Test","text":"Submit the live URL. Confirm the Article type is detected and zero errors are reported."}]}]}
§3.1·ARTICLE
PublishedVerifiedEvery 6 weeksSources5 namedAuthored bySquareRank Team
Schema · § 3.1 · How-to
Article schema for Squarespace blog posts
Article schema is the JSON-LD block that tells Google and AI engines this page is an article — a blog post, an editorial guide, a long-form how-to — and names the author, publisher, and dates. Google's canonical guidance1 says Article has zero required fields, but the recommended set (author, datePublished, dateModified, headline, image) is what AI engines look for. On Squarespace, install via Page Settings > Advanced > Code Injection > Header, with the author pointing to your founder Person entity at /founder/.
This leaf ships the copy-paste block, the Squarespace placement, the validation pass, and the three Squarespace-specific gotchas that catch first-time installs. The schema layers cleanly on top of Squarespace's auto-emitted BlogPosting block on blog templates — the trick is not duplicating fields.
§01Definition
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.
The vocabulary lives at schema.org/Article2, with the inheritance chain Thing > CreativeWork > Article. Subtypes inherit every property and add a few of their own — NewsArticle adds dateline, BlogPosting adds nothing material. For a typical Squarespace blog post, BlogPosting is the cleanest choice because it aligns with what the platform auto-emits.
§02When
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.
A common over-application: putting Article schema on a service landing page because it has a few paragraphs of copy. That misrepresents the page to the search engine and confuses the entity model. The right schema for a service landing page is Service; for a product page, Product; for the homepage, Organization plus optionally WebSite.
§03Rich results
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.
The honest framing is “helpful for Google, important for AI engines.” Article schema rarely changes whether a page ranks in Google — the page either ranks because the content is strong or it doesn't — but it consistently changes whether AI engines attribute a citation to the page or to a competitor whose entity model is murkier.
Article schema in 2026
0
required Article fields per Google's canonical structured-data documentation (everything is recommended).
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.
headline — the title of the page. Plain text. Keep under 110 characters for safe display.
author — a Person object. Set name and url; the url points to your founder bio page at /founder/.
publisher — an Organization object. Set name (your brand) and url (your homepage). Optionally include a logo.
datePublished — ISO 8601 date string when the article was first published.
dateModified — ISO 8601 date string when the article was last meaningfully updated. Bump this on real edits, not on cosmetic changes.
image — a fully-qualified URL to a representative image, or an ImageObject with url, width, height.
mainEntityOfPage — the canonical URL of the page itself. Resolves ambiguity when the article is syndicated.
description (optional) — a 1-2 sentence summary. Worth including for AI engine extraction.
§05Example
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.
JSON-LDBlogPosting schema for a Squarespace blog post — replace placeholder values
<script type="application/ld+json">{"@context":"https://schema.org","@type":"BlogPosting","headline":"Coastal palettes that photograph well in low light","description":"The five paint and fabric pairings we keep coming back to for north-facing rooms on the Maine coast.","datePublished":"2026-05-12","dateModified":"2026-05-18","image":"https://yoursite.com/images/coastal-palette-hero.jpg","author": {"@type":"Person","name":"Margaret Hollis","url":"https://yoursite.com/founder/"},"publisher": {"@type":"Organization","name":"Hollis Coastal Interiors","url":"https://yoursite.com/","logo":"https://yoursite.com/images/logo.png"},"mainEntityOfPage":"https://yoursite.com/blog/coastal-palettes-low-light"}</script>
§06Install
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.
The Page Header injection ensures the schema loads per-page — you get a different Article block on every blog post, which is correct. The sitewide alternative (Settings > Advanced > Code Injection > Header) is wrong for Article schema because it would inject the same Article block onto every page on the site, including the homepage and contact page. Use sitewide only for Organization and the BreadcrumbList rules; use per-page for Article, Service, Product, Event, Person.
Verify after saving: open the published page in a new tab, view source (Ctrl+U on Windows, Cmd+Option+U on Mac), and find-on-page for application/ld+json. Your block should appear once. If two blocks appear, Squarespace's auto-emitted BlogPosting is duplicating yours — see the gotcha below.
§07Validation
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.
For a deeper structural check, submit the page to the Schema.org validator at validator.schema.org. The Schema.org validator parses against the full Schema.org vocabulary, catching errors Google's tool sometimes misses (typed properties used in the wrong place, deprecated property names). For most Squarespace work, the Rich Results Test is sufficient; pull the Schema.org validator out when you're authoring a complex @graph with multiple entities.
§08Gotchas
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.
A fourth gotcha specific to AI engine citation: pointing author at a bare Person object with just a name. AI engines weight entity-linked authors much more heavily than anonymous ones — a Person object with url pointing to your founder bio page (which itself carries Person schema with sameAs links to LinkedIn, etc.) gives the AI a graph it can confidently attribute. A bare "name": "Jane Smith" with no url gets ignored. The fix is to set every Article's author.url to /founder/ and ship the full Person schema there. The pattern is documented in the Person (author) leaf.
§09Related
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).
