Essential Bolt CMS Extensions Setup & Verification Guide
Every modern production website built with Bolt CMS requires four foundational extensions for discoverability, search engine indexing, AI crawler readiness and visitor statistics:
AppoloDev/bolt-seo(appolodev/bolt-seo): Structured SEO meta fields (type: seo), OpenGraph tags, JSON-LD, and robots meta tags — plus a theme override that gives<link rel="canonical">,og:urlandtwitter:urlone clean URL (bolt/core PR #3735 workaround).Vondry/bolt-sitemap(tomvondracek/bolt-sitemap): an XML sitemap index generated from content and routes, including the theme's static pages. It needs no theme override and replacesbolt/sitemap-extension.Vondry/bolt-llms-txt(tomvondracek/bolt-llms-txt): Serves/llms.txtdynamically from CMS content adhering strictly to the llmstxt.org specification.Vondry/bolt-server-analytics(tomvondracek/bolt-request-analytics): Cookieless visitor statistics built on the server from the HTTP request alone — no JavaScript, no cookies, no identifiers, so nothing for the consent banner. A dashboard card and an Analytics page in the backend; redirects from alias domains are counted.
This skill provides the end-to-end installation steps, architecture patterns, theme templates, and an automated verification script.
1. AppoloDev/bolt-seo Setup
Official repository: AppoloDev/bolt-seo
1.1 Install via Composer
composer require appolodev/bolt-seo:^2.31.2 Copy Config Recipes & Install Assets
php bin/console extensions:configure --with-config
php bin/console assets:install --symlink --relative publicThis generates:
config/extensions/appolo-boltseo.yamlconfig/packages/extension_bolt-seo.yaml- Publishes JavaScript/CSS assets to
public/assets/seo/for the Bolt editor backend.
1.3 Configure Fallback Fields
In config/extensions/appolo-boltseo.yaml, define field fallback chains so that if an editor leaves the SEO field blank, title, description, and preview images fall back naturally to record fields:
# config/extensions/appolo-boltseo.yaml
title_separator: "|"
title_postfix: ''
title_length: 70
description_length: 158
fields:
slug: [ 'slug' ]
title: [ 'title', 'name', 'heading' ]
description: [ 'introduction', 'teaser', 'description', 'hero_subtitle' ]
keywords: [ ]
image: [ 'image', 'main_image', 'photo' ]
default:
title: ""
description: ""
keywords: ""
ogtype: "website"
robots: "index, follow"
templates:
meta: partials/_seo_metatags.twig # canonical override: set it once the partial exists, section 1.6The robots default is default.robots. A top-level meta_robots key and the commented-out allow: block from older recipes were never read, and bolt-seo 2.3 removed both from its own config. Delete them from projects that still carry them; nothing renders differently, because index, follow is also the built-in fallback.
1.4 Integrate Reusable SEO Field in contenttypes.yaml
Following the bolt-contenttypes best practice, declare a reusable anchor under __nodes and merge it into every routable ContentType:
# config/bolt/contenttypes.yaml
__nodes:
common_fields: &common_fields
title:
type: text
group: meta
label: "Název"
localize: true
required: true
slug:
type: slug
uses: [ title ]
group: meta
seo_field: &seo_field
seo:
type: seo
group: seo
localize: true
homepage:
name: Domovská stránka
singular_name: Domovská stránka
singleton: true
order: -id
fields:
<<: [ *common_fields, *seo_field ]
articles:
name: Články
singular_name: Článek
fields:
<<: [ *common_fields, *seo_field ]1.5 Include SEO Tags in Theme Base Layout
The shared layout shell public/theme/<themename>/partials/_master.twig created by bolt-theme-init already contains this block inside <head> (Integration Contract in WORKFLOWS.md); for a theme without it, place the SEO block inside the HTML <head> of the base layout:
{# https://github.com/AppoloDev/bolt-seo #}
{% block seo %}
<title>{{ seo.title() }}</title>
{{ seo.metatags() }}
{% endblock seo %}For static or helper pages without a CMS record, override the block in that template:
{% block seo %}
{% set seoTitle = __('page.title') ~ ' | ' ~ config.get("general/sitename") %}
<title>{{ seoTitle }}</title>
{% include '@seo/_metatags.html.twig' with {
title: seoTitle,
description: __('page.seo.description'),
keywords: __('page.seo.keywords'),
canonical: seo.canonical()
} %}
{% endblock seo %}Pass canonical: seo.canonical(), the URL <link rel="canonical"> prints. Do not pass app.request.uri: it carries the query string (?utm_source=…), which the canonical drops, so og:url would differ from the canonical on every tagged link.
1.6 Canonical URL Override (bolt/core PR #3735 Workaround)
[!IMPORTANT] Until bolt/core Pull Request #3735 is merged and the project runs a bolt/core release that includes it, every Bolt 6 project needs this override. Bolt's canonical URL (bolt/core ≤ 6.1.10):
- names a singleton by its record route, e.g.
/kontakt/kontakt-2, although visitors use/kontakt(localized:/en/kontakt/kontakt-2);- keeps the listing query on a listing page, e.g.
/clanky?order=-createdAt&status=published.bolt-seo 2.3 builds
og:urlandtwitter:urlfrom the same Bolt canonical, so both problems show up in<link rel="canonical">,og:urlandtwitter:url. A theme that corrects only<link rel="canonical">(its owncanonical_template) makes it worse:og:urlthen names a different URL than the canonical.The Workaround: one macro corrects Bolt's canonical the way PR #3735 does, and both
<link rel="canonical">and bolt-seo'sog:url/twitter:urlprint its result. The three tags always name the same URL.
Copy the three files from examples/ to public/theme/<themename>/partials/ unchanged, before the config below names them: neither Bolt nor bolt-seo falls back when the template is missing, and every page fails to render. They are identical in every project, so the removal later is the same everywhere:
| File | Role |
|---|---|
_canonical.macros.twig |
The correction. On a listing or record route it drops a singleton's record slug and a listing's query. A canonical set explicitly is kept as written. |
_canonical.twig |
<link rel="canonical">, Bolt's canonical_template. |
_seo_metatags.twig |
bolt-seo's templates.meta. It includes the stock @seo/_metatags.html.twig with canonical replaced, so upstream template changes still arrive. |
Point Bolt and bolt-seo at them:
# config/bolt/config.yaml
# Workaround until https://github.com/bolt/core/pull/3735 is released, see
# partials/_canonical.macros.twig in the theme. Named through @theme: Bolt also renders it into
# redirects it answers without rendering a page, before the theme folder is on Twig's path.
canonical_template: '@theme/partials/_canonical.twig'# config/extensions/appolo-boltseo.yaml
# Renders bolt-seo's own template with og:url and twitter:url set to the same URL as
# <link rel="canonical">, until https://github.com/bolt/core/pull/3735 is released.
templates:
meta: partials/_seo_metatags.twigRules:
@theme/, not a bare theme path, incanonical_template(and in_canonical.twig's import). Bolt adds the theme folder to Twig's default path only when a controller renders a page. For an unsupported locale (/?_locale=de, or a record under/<locale>/that its ContentType'slocaleslack) the controller answers a redirect to the default locale without rendering, yet the canonical widget still renderscanonical_templateinto that response. A barepartials/_canonical.twigis then not found and the redirect becomes a 500 that anyone can trigger with a query string.@theme(registered inconfig/packages/twig.yaml) always resolves.verify.shfails on the bare path and, withBOLT_BASE_URL, requests/?_locale=<unknown>, which must redirect.- Never fix a mismatch in the admin. The SEO field's "Canonical Link" (and
override_default.<route>.canonical) is meant for a page that really belongs under another URL. With the override it sets<link rel="canonical">,og:urlandtwitter:urlalike, as written. Without the override it sets onlyog:url/twitter:url. Typing the clean URL into every record per locale would hard-code the host, miss listings (no record) and go stale. - Pages that include
@seo/_metatags.html.twigthemselves passcanonical: seo.canonical()(section 1.5). On their static routes the canonical needs no correction, and the line survives the removal. - Check it: with
bin/console cache:pool:clear cache.appfirst (Bolt caches canonical links for 60 seconds, andcache:cleardoesn't empty that pool), compare<link rel="canonical">withog:urlon a singleton page, its translation and a listing. They must be equal, slugless and without?order=…, and the URL must answer 200.
Removing it once the project runs a bolt/core release with PR #3735: delete the three partials, canonical_template from config/bolt/config.yaml and templates from config/extensions/appolo-boltseo.yaml, then run the check above again. Until then the macro is a safe no-op on an already clean canonical, so a forgotten copy renders the same URLs. After the removal the admin "Canonical Link" sets only og:url again, so leave it empty.
2. Vondry/bolt-sitemap Setup
Official repository: Vondry/bolt-sitemap (package tomvondracek/bolt-sitemap)
It replaces bolt/sitemap-extension and needs no theme template. Out of the box it lists:
- one
<url>per page and locale with reciprocalhreflangalternates andx-default; - singletons at their slugless URL (
/kontakt, not/kontakt/kontakt-2); - listing pages with alternates on the listing route;
- the static pages (
TemplateControllerroutes, section 2.4); - images, and an honest
<lastmod>(none where no date is known).
Pages that bolt-seo marks noindex or gives another canonical URL are left out. /sitemap.xml is a sitemap index with child sitemaps:
/sitemap-main.xml: homepage, singletons and static pages;/sitemap-<contenttype>.xml: one per ContentType.
2.1 Install via Composer
composer require tomvondracek/bolt-sitemap:^1.0bolt/sitemap-extension must not be installed: both serve /sitemap.xml, and the package declares a conflict. To migrate an existing project, see section 2.6.
2.2 Copy Config Recipes
php bin/console extensions:configure --with-configThis generates:
config/extensions/tomvondracek-sitemap.yamlconfig/packages/extension_bolt-sitemap.yaml(cache invalidation on content changes,@bolt-sitemapTwig namespace)config/routes/extension_bolt-sitemap.yaml(/sitemap.xml,/sitemap-<name>.xml)
2.3 Configure the Extension
Replace the generated config/extensions/tomvondracek-sitemap.yaml with examples/tomvondracek-sitemap.yaml. The defaults are right for most sites, and the example documents every key a project usually sets:
# config/extensions/tomvondracek-sitemap.yaml
listings: true # listing pages of ContentTypes that show published records
exclude_contenttypes: [] # ContentTypes whose records are left out (their listing stays)
exclude_listings: [] # ContentTypes whose listing page is left out
taxonomies: [] # e.g. [categories, tags]
# Static pages (section 2.4): every TemplateController route without parameters.
static_routes: true
exclude_static_routes: [] # route names, e.g. [thank_you, thank_you_locale]
static_route_lastmod: {} # route name => date of the page's last content change
images:
enabled: true
fields: {} # ContentType => image/imagelist fields; default: the record's first image
seo:
respect_noindex: true # leave out pages bolt-seo marks noindex or canonicalizes elsewhere
human_view:
stylesheet: false # browsers show the raw XML; true = styled list (/sitemap.css)
script: false # true = table with links (/sitemap-ui.js)- Images: set
images.fields.<contenttype>when the first image is not the one that represents the page. A decorative badge or icon is a bad pick; usehomepage: []to list none, orproducts: [image, gallery]to list a gallery. exclude_contenttypes/exclude_listings: use them only for pages that exist but should not be in search, such as internal listings. Viewless ContentTypes,viewless_listing: trueandhide_listing_from_xml_sitemap: trueare already honoured.- Don't override the sitemap templates to fix URLs. The fixes the old
extensions/sitemap.xml.twigoverride carried are built in. If a URL must be added or dropped, use the extension'sSitemapUrlsEvent(see its README).
2.4 Static Pages Are in the Sitemap Through Their Routes
[!IMPORTANT] Static pages (
static-pages/<name>.twigin the theme, e.g. the privacy policystatic-pages/gdpr.twig) have no ContentType. The sitemap finds them only through theirTemplateControllerroutes inconfig/routes.yaml(WORKFLOWS.md, Static Routes). Every static page needs:
- a route without parameters pointing at its template (
templateName: static-pages/<name>.twig), above thefrontend:import. That route is the page's URL in the default locale;- on a multilingual site, the
<name>_localetwin with path/{_locale}/…,requirements: { _locale: '%app_locales%' }and the sametemplateName. The sitemap pairs the two by template and lists/en/…,/de/…as the page's other languages withhreflangalternates. A twin with another template is a different page, and a page without a twin is listed in the default locale only.
# config/routes.yaml (above the frontend: import)
privacy:
path: /zasady-ochrany-osobnich-udaju
defaults:
_controller: Bolt\Controller\Frontend\TemplateController::template
templateName: static-pages/gdpr.twig
privacy_locale:
path: /{_locale}/zasady-ochrany-osobnich-udaju
requirements: { _locale: '%app_locales%' }
defaults:
_controller: Bolt\Controller\Frontend\TemplateController::template
templateName: static-pages/gdpr.twigRules:
- Keep
static_routes: truewhenever the theme hasstatic-pages/. Never list static pages by hand: a new route appears in the sitemap automatically. - Pages that must not be indexed (thank-you pages, form confirmations) belong in
exclude_static_routes(both route names), or getrobots: 'noindex, follow'in bolt-seo'soverride_default.<route name>. The sitemap follows that too, so the page's<meta name="robots">and the sitemap agree. <lastmod>: a static page has none by default, because its template's file time is the time of the last deploy, not of a content change. To give one, setstatic_route_lastmod: { privacy: 2026-10-01 }and update the date when the page's text changes.- Redirect routes (
RedirectController) and routes with parameters are never listed.
2.5 Name the Sitemap in robots.txt
Crawlers look for the sitemap in robots.txt; without the line it is found only through Search Console. public/robots.txt (Symfony's default file, served by Apache as a static file) gets one absolute line — the Sitemap: directive does not accept a relative path:
User-agent: *
Sitemap: https://example.cz/sitemap.xmlUse the canonical host (BOLT_CANONICAL). The line names the index; crawlers follow it to the child sitemaps. Don't serve a static public/sitemap.xml: Apache would deliver it before Bolt sees the request.
2.6 Migrating a Project from bolt/sitemap-extension
composer remove bolt/sitemap-extension, then sections 2.1–2.3.- Delete the theme override (
extensions/sitemap.xml.twigor_sitemap.xml.twig) andconfig/extensions/bolt-sitemapextension.yaml. - Delete a hand-written list of static routes from the old override. Check section 2.4 instead: every static page has its route and, on multilingual sites, its
_localetwin with the same template. - Check that
config/packages/extension_*.yamlandconfig/routes/extension_*.yamlof the other extensions are still there. When Bolt's post-update script can't boot the container in the middle of the swap, it removes them;php bin/console extensions:configurerestores them. - Compare the old and the new URL set. Expect the same pages, plus one
<url>per extra locale, and without duplicate listing entries.
3. Vondry/bolt-llms-txt Setup
Official repository: Vondry/bolt-llms-txt (package tomvondracek/bolt-llms-txt)
3.1 Install via Composer
composer require tomvondracek/bolt-llms-txt:^1.13.2 Copy Config Recipes
php bin/console extensions:configure --with-configThis generates:
config/extensions/tomvondracek-llmstxt.yamlconfig/packages/extension_bolt-llms-txt.yamlconfig/routes/extension_bolt-llms-txt.yaml
3.3 Configure the Extension
In config/extensions/tomvondracek-llmstxt.yaml:
# config/extensions/tomvondracek-llmstxt.yaml
enabled: true
template: '@theme/extensions/llms.txt.twig'
locale: en # 'en' when the site has English (AI crawlers read it best); otherwise leave empty for the default locale
max_age: 36003.4 Create llms.txt.twig in the Theme Extensions Folder
Place the template in the theme's extensions folder:
public/theme/<themename>/extensions/llms.txt.twig.
3.5 Specification Formatting Guidelines (llmstxt.org)
[!IMPORTANT] The reference implementation parser on llmstxt.org enforces strict syntactic rules:
- File must start with an H1 header:
# <Sitename>- Immediate single-line blockquote:
> <Brief summary of site/business>- Introductory Context: Free Markdown with NO H2 or H3 headers (use bold labels like
**Contact:**).- H2 Sections: Every H2 section (
## Section Title) MUST contain ONLY bullet items in- [Title](URL): Descriptionformat. Any non-list lines inside an H2 block fail parser validation.## OptionalSection: Standardized bucket for secondary pages, external registers, and the sitemap.- Twig Autoescaping: The
.txt.twigextension switches autoescaping off. Always run CMS values through the extension's provided filters:|html_to_text,|markdown_label, and|markdown_url.
3.6 Production Template Blueprint
The template below uses the field names of the bolt-contenttypes blueprint (homepage.hero_title, homepage.hero_intro, settings.email, settings.phone, articles.teaser) with theme.yaml contact fallbacks; map them to the site's ContentTypes. The extension's own generic template (vendor/tomvondracek/bolt-llms-txt/templates/llms.txt.twig) lists every listable ContentType automatically and is a good reference for larger sites.
{# public/theme/<themename>/extensions/llms.txt.twig #}
{#- llms.txt (https://llmstxt.org) — served at /llms.txt by tomvondracek/bolt-llms-txt
Placed in: public/theme/<theme_name>/extensions/llms.txt.twig
Layout follows the llmstxt.org specification:
1. H1 title (# Sitename)
2. A single-line blockquote (> Summary)
3. Markdown body describing the project, services, and contacts (NO H2/H3 headings here)
4. H2 sections (## Section Name) containing ONLY bullet items in "- [Title](URL): Description" format.
The reference parser fails on any other line inside an H2 section.
5. An optional ## Optional section for secondary resources and sitemap.
Field names match the bolt-contenttypes blueprint: `homepage` singleton (hero_title,
hero_intro), `settings` singleton (email, phone) and `articles` (teaser). Contact
fallbacks come from theme.yaml (contact.*). Adapt the names to the site's ContentTypes.
Autoescaping is off for .txt templates; every CMS value goes through html_to_text,
markdown_label or markdown_url. Variables: today (Y-m-d), now, baseUrl, locale.
-#}
{%- autoescape false -%}
{#- setcontent throws for an unknown ContentType: query only the ones the site defines. -#}
{%- set homepage = null -%}
{%- set settings = null -%}
{%- set articles = [] -%}
{%- if config.get('contenttypes/homepage') -%}{%- setcontent homepage = 'homepage' -%}{%- endif -%}
{%- if config.get('contenttypes/settings') -%}{%- setcontent settings = 'settings' -%}{%- endif -%}
{#- `page 1`, so `?page=` in the URL can never select another page of records. -#}
{%- if config.get('contenttypes/articles') -%}{%- setcontent articles = 'articles' limit 50 page 1 -%}{%- endif -%}
{#- `??` keeps the template working when a singleton record does not exist yet. -#}
{%- set email = (settings.email ?? '')|default(config.get('theme/contact/email')) -%}
{%- set phone = (settings.phone ?? '')|default(config.get('theme/contact/phone')) -%}
{%- set hero_title = homepage.hero_title ?? '' -%}
{%- set hero_intro = homepage.hero_intro ?? '' -%}
{%- set address = config.get('theme/contact/address') -%}
{%- set summary = (hero_intro|default(hero_title)|default(config.get('general/payoff')))|html_to_text(200) -%}
# {{ config.get('general/sitename')|html_to_text }}
{% if summary is not empty %}
> {{ summary }}
{% endif %}
This file is generated from the website's content management system; the facts below are what the website showed on {{ today }}.
{% if hero_title is not empty %}
**About:**
- {{ hero_title|html_to_text }}
{% endif %}
{% if email or phone or address %}
**Contact:**
{% if email %}
- Email: {{ email|html_to_text }}
{% endif %}
{% if phone %}
- Phone: {{ phone|html_to_text }}
{% endif %}
{% if address %}
- Address: {{ address|html_to_text }}
{% endif %}
{% endif %}
## Website pages
- [Homepage]({{ baseUrl }}/): the website's main page.
{% if articles is not empty %}
## Articles
{% for article in articles %}
- [{{ article|title|markdown_label }}]({{ article|link(true)|markdown_url }}){{ article.teaser is defined and article.teaser is not empty ? ': ' ~ article.teaser|html_to_text(200) }}
{% endfor %}
{% endif %}
## Optional
- [Sitemap]({{ baseUrl }}/sitemap.xml): XML sitemap of all published pages.
{% endautoescape %}4. tomvondracek/bolt-request-analytics Setup
Official repository: Vondry/bolt-server-analytics (package tomvondracek/bolt-request-analytics)
After a page has been sent, the request is classified (path, device, browser, language, source) and appended to a spool file; a rollup moves the spool into a database of its own when an admin opens the dashboard, or from cron. The IP address is never read and nothing identifies a visitor, so it needs no consent and does not belong in the cookie banner. It needs no theme template.
4.1 Install via Composer
composer require tomvondracek/bolt-request-analytics:^1.0It pulls in symfony/lock. Its Flex recipe adds config/packages/lock.yaml (framework.lock: '%env(LOCK_DSN)%') and LOCK_DSN=flock to .env; keep both and commit symfony.lock. Bolt's post-install script adds the TomVondracek\RequestAnalytics\ resource to config/services_bolt.yaml.
4.2 Copy Config Recipes & Keep the Data out of Git
php bin/console extensions:configure --with-config
php bin/console request-analytics:install # creates the tables now (otherwise on first use)
php bin/console cache:clearThis generates:
config/extensions/tomvondracek-requestanalytics.yamlconfig/packages/extension_bolt-request-analytics.yaml(translations,@request-analyticsTwig namespace, the Analytics menu item)config/routes/extension_bolt-request-analytics.yaml(the backend page and its API)
Visits wait in var/request-analytics/spool/ and the statistics live in var/data/request-analytics.db. Neither belongs in Git, and the database is not Bolt's:
# .gitignore
/var/data/*
/var/request-analytics/4.3 Configure the Extension
Replace the generated config/extensions/tomvondracek-requestanalytics.yaml with examples/tomvondracek-requestanalytics.yaml and fill in the hosts. Every key it leaves out keeps the extension's default:
# config/extensions/tomvondracek-requestanalytics.yaml
enabled: true
access:
view: [ROLE_ADMIN]
delete: [ROLE_ADMIN]
own_hosts: [example.cz, www.example.cz] # the canonical host (BOLT_CANONICAL) and its www twin
aliases:
hosts: [] # section 4.4
target: https://example.cz
mode: count
redirect_status: 301
storage:
database: '%kernel.project_dir%/var/data/request-analytics.db'
aggregation:
trigger: admin # cron / both with the cron job of section 4.5
privacy:
honor_gpc: true
honor_dnt: true
retention_months: 25own_hosts: always the canonical host and the www twin. Without them a click fromwww.example.cz(before its redirect) or a proxy'sHostis counted as a referral from another site.storage.database: keep the SQLite default unless the host has nopdo_sqlite; then a MySQL / PostgreSQL database of its own through'%env(REQUEST_ANALYTICS_DATABASE_URL)%', defined in the server's.env.local. Bolt's own database is refused, and so is any path inpublic/.access.view:ROLE_ADMINby default. AddROLE_CHIEF_EDITORonly when the client's editors should see the numbers.
4.4 Domain Aliases (Second Domains That Redirect to the Site)
A second domain (example-alias.cz → example.cz: a spelling without the hyphen, an old domain, a campaign domain) never shows up as a Referer, so the extension counts the redirect itself:
aliases:
hosts: [example-alias.cz, www.example-alias.cz]
target: https://example.cz # BOLT_CANONICAL
mode: countIn count mode the alias domain must reach this application (DNS to the same hosting, the alias attached to the webhosting, a TLS certificate for it), and Symfony must trust its Host, or Symfony answers HTTP 400:
# .env — one pattern for the canonical and the alias hosts (bolt-security-hardening Step 1)
SYMFONY_TRUSTED_HOSTS='^(www\.)?(example|example-alias)\.cz$'Rules:
- Don't redirect the alias at the registrar or in
.htaccessincountmode: the request then never reaches Bolt and is not counted. The root.htaccesswww → bare host redirect (bolt-htaccessStep 1) is fine:www.example-alias.cz→example-alias.cz→ the extension's counted 301 to the target. - When the redirect has to stay elsewhere (a registrar's forwarding, another server), use
mode: tagand let that redirect go tohttps://example.cz/?ra_via=example-alias.cz. The same marker counts QR codes and print:aliases.hosts: [poster-a2]andhttps://example.cz/?ra_via=poster-a2. - No alias: leave
hosts: [].
4.5 Production
- Cron (recommended on busy sites, or when nobody logs in for weeks):
0 * * * * cd /path/to/project && bin/console request-analytics:rollupas the web server's user (a file created by another user that the web server can't write stops the statistics), andaggregation.trigger: both. - Timezone: days and hours follow
timezoneinconfig/bolt/config.yaml(bolt-timezone). - Deploys with release directories: share
var/request-analytics/andvar/data/. An SFTP upload never overwrites them as long as they are not in the repository. - Privacy policy: always name the statistics. They are built from the same requests as the server logs, so the privacy page's
web_operationpurpose (bolt-cookie-consent) gets one clause in its data: „…typ prohlížeče (serverové logy); z požadavků se dále sestavuje anonymní statistika návštěvnosti bez IP adresy a identifikátorů“ (en: “…; anonymous visitor statistics without IP addresses or identifiers are also compiled from the requests”).bolt-cookie-consent'sprivacy-config.phpappends it when the extension is installed; in an existingtheme.yamlor privacy record, append it by hand and increaseconfig_version. Itsverify.shfails while the privacy page lacks it. The statistics set no cookie and need no consent, so they add nothing to the banner or the cookie table. - Testing: nothing is collected with
APP_ENV=devorAPP_DEBUG=1. Check collection on production, or locally withAPP_ENV=prod APP_DEBUG=0and a cleared cache: open a page, then the dashboard — the card shows today's page view.
5. Automated Verification Script
To verify that all four extensions and their theme overrides are correctly wired:
vendor/tomvondracek/bolt-skills/skills/bolt-extension-setup/scripts/verify.shWhat the script verifies:
- Composer packages: Verifies
appolodev/bolt-seo,tomvondracek/bolt-sitemap, andtomvondracek/bolt-llms-txtare installed. Fails whenbolt/sitemap-extensionis still installed. - Configuration files: Confirms
appolo-boltseo.yaml,tomvondracek-sitemap.yaml, andtomvondracek-llmstxt.yamlexist underconfig/extensions/. Warns about a leftoverbolt-sitemapextension.yaml. - Recipes: Checks package and route configurations in
config/packages/andconfig/routes/(bolt-seo, bolt-sitemap, bolt-llms-txt). - ContentType Schema: Validates that
type: seois present inconfig/bolt/contenttypes.yaml(and recommendsseo_field: &seo_field). - Theme SEO Integration: Checks
<head>in theme layouts for{{ seo.metatags() }}. - Theme Extensions Directory:
- Warns about a leftover sitemap override (
extensions/sitemap.xml.twigor_sitemap.xml.twig) frombolt/sitemap-extension(section 2.6). - Static pages (section 2.4): fails when a
static-pages/*.twigtemplate has noTemplateControllerroute, because it is then neither served nor in the sitemap. On a multilingual site, warns when its_localetwin is missing, and warns whenstatic_routes: falsehides the static pages. - Verifies
llms.txt.twigexists inpublic/theme/<themename>/extensions/and follows thellmstxt.orglayout. - Warns when
public/robots.txtis missing or has no absoluteSitemap: …/sitemap.xmlline (section 2.5), or when a staticpublic/sitemap.xmlshadows the extension.
- Warns about a leftover sitemap override (
- Canonical URL override (section 1.6, until bolt/core PR #3735 is released):
- Fails when
partials/_canonical.twig,_canonical.macros.twigor_seo_metatags.twigis missing, or whencanonical_template/templates.metadoesn't point at them. Warns when a copy differs from the skill example. - Warns when a theme template passes
canonical: app.request.urito the meta tags (section 1.5), orappolo-boltseo.yamlstill has the deadmeta_robots/allowkeys (section 1.3).
- Fails when
- Request analytics (section 4): warns when
tomvondracek/bolt-request-analyticsis not installed. Once it is, fails when its config, package or route recipe or itsservices_bolt.yamlentry is missing, whenSYMFONY_TRUSTED_HOSTSrejects an own host or acount-mode alias host (HTTP 400), whenaliases.targetis empty with alias hosts, when the database or spool is inpublic/, or whenlock.yamlreads an undefinedLOCK_DSN. Warns whenown_hostsis empty or lacks theBOLT_CANONICALhost, and when.gitignorelacks/var/request-analytics/or/var/data/*.