SEO and indexing for Sites

​

Where to set a Site’s SEO

​

Which value wins

1. config/meta.json routeMeta, then pages, for the page’s exact path. This is your code’s per-page override.
2. The Site’s SEO settings, from the admin, Mist or the API.
3. config/meta.json default.
4. The Site’s own title, description and image, then your store’s defaults.

​

The page metadata file

{
  "default": {
    "title": "Diamond Leaders",
    "description": "Events and training for the Diamond Leaders team.",
    "image": "/og.png"
  },
  "url": "https://yoli.com/home/sites/diamond-leaders",
  "twitter": { "site": "@yoli" },
  "routes": ["/events", "/drafts"],
  "routeMeta": {
    "/events": { "title": "Events", "description": "Team calls and launches this month." },
    "/drafts": { "noindex": true }
  }
}

​

Add SEO at build time with fluidSite()

import react from "@vitejs/plugin-react";
import { fluidSite } from "@fluid-app/sites/vite";
import { defineConfig } from "vite";

export default defineConfig({
  plugins: [react(), fluidSite()],
});

• Head tags in index.html: the title, description, Open Graph tags and Twitter card. A title from config/meta.json replaces the page’s <title>. With no title, the page keeps its own.
• One index.html per route, such as events/index.html, with that route’s own tags. Routes come from routes, plus any plain path: "/…" literal in src/router.ts or src/routes.ts. The Site serves a route’s own file before the single-page app fallback.
• Page content. With the prerender option, a module that exports render(path), each page’s HTML goes inside the root element. Without it, each page gets a <noscript> with its title and description.
• llms.txt, listing the home page and every route.
• sitemap.xml, only when config/meta.json has an absolute url. A sitemap needs absolute addresses.

​

Indexing

• it’s a company Site, not a member’s Site and not a branch;
• it’s public, switched on, not taken down, and published;
• indexing is turned on in its SEO settings: Show in search engines in the admin or Mist, or indexable: true with the API;
• your store doesn’t block indexing for the whole storefront.

• X-Robots-Tag: noindex, nofollow on every answer of a Site that isn’t indexable.
• robots.txt. For a Site that isn’t indexable, one that disallows everything, whatever the build ships. For an indexable Site, the build’s own robots.txt, or on its standalone host a generated one that allows everything and names the sitemap.
• sitemap.xml and llms.txt. None for a Site that isn’t indexable: they answer not found. For an indexable Site, the build’s own files, or on its standalone host files generated from routes in config/meta.json.
• A canonical Link header on each page of a standalone Site, naming the page’s storefront address. For a company with no storefront, the standalone address is the canonical one.