SEO here means how each page presents itself to search engines and social networks. In Velk it needs no plugin. Every page, and every item of a content type with its own address (a post, a service, a product), comes with three fields in a section of the admin called SEO & sharing, labelled in the admin's language since v3.9.1. Velk also serves an always up-to-date sitemap.xml and works out the canonical address of each page. The client writes the titles and descriptions; the AI makes the theme print them.
The three built-in fields
| Field | What it does |
|---|---|
| Meta title | Shown in the browser tab and in search results. Left blank, the content's title is used. |
| Meta description | A short summary, up to about 160 characters, for search results and link previews. |
| Share image | Appears when the link is shared on social networks and WhatsApp. Recommended size: 1200×630. |
Ask the AI
Before we launch the bakery site, review its SEO: every page and product must print the meta title, description and share image from the SEO & sharing section, falling back to the title, the summary and the product photo when they're blank. Check the canonical tag and the sitemap. Don't create new SEO fields.
The AI reads the theme's head, the invisible top of each page where these tags live, fixes what's missing and shows you one page's tags.
What Velk generates
- The sitemap at
/sitemap.xml, the list of addresses search engines read: every page, every published item of the types with their own page, and the category and tag pages. Drafts, the 404 page and anything set tohas_page: falsestay out. On a site in several languages, each address lists its versions in the other languages (hreflang) and which one is the default. - The canonical address, which tells search engines which URL is the real one. The theme prints it next to the language versions. Since v3.9.0 these no longer repeat the language prefix (
/en/en/…). - One address per language. Content without a translated address opens at its default address in the other language (since v3.9.0); once translated, the old one stops answering there, so there are no duplicate pages.
The site's address: APP_URL
Full addresses (in the sitemap, the canonical tag, the share image) come from APP_URL, a line in .env, the site's settings file: scheme and domain only, like https://example.com, never a subfolder. On your computer it can stay blank; on the first deploy, the AI asks for the site's address and writes it on the server.
Choose one version, with or without www, always with https, and use it everywhere. Redirecting the other versions to it is set up in the hosting or the CDN, not in Velk. If the domain changes, ask the AI to update APP_URL and robots.txt on the server.
robots.txt
robots.txt is the public file that tells crawlers what to visit and where the sitemap is. It's created at install, the first deploy writes the real sitemap address in it, and Velk updates never touch it. Leave the admin out: since v3.8.1 the admin asks search engines not to index it, and a line blocking it would stop crawlers from seeing that request and give its address away. If Velk lives in a subfolder, crawlers only read the domain's root robots.txt, so submit the sitemap in Google Search Console.
The 404 page
An address that doesn't exist shows Velk's plain 404 until you ask for one of your own. The AI creates a page with its own template and editable fields and points not_found_page in site.json at it. That page answers with the 404 status search engines expect, has no address of its own and stays out of the sitemap. Since v3.9.0, a template missing from the theme also leads there instead of an error page.
Ask the AI
Create a 404 page for the clinic site: a short headline, one sentence and two buttons, one to the home page and one to book an appointment. The clinic should be able to edit the texts in the admin.
The AI adds the page to site.json, writes its template and runs schema:validate, which also catches a not_found_page pointing at a page that doesn't exist.
Questions
I published a post. Why isn't it on Google yet?
The sitemap lists it as soon as it's published, but Google decides when to visit. Submit the sitemap once in Search Console to follow how it's read.
Where do category pages get their title and description?
Categories have no SEO section: the theme uses the category's name. To write a description for each, ask the AI for a description field on the taxonomy, used in the page's tags.