Give your content a clear signal.
Metadata, structured data and connected URLs. A technical foundation for a website that speaks clearly to people and search engines.
Explore the SEO system ↓A strong website has more than a beautiful face.
Visitors see the layout, photographs and words. Search systems also need to understand what the page represents, which address is its main version and how it relates to the rest of the website. Those details live beneath the visible interface, but they deserve the same care as the design.
Wulver brings these decisions into a shared technical foundation. Page metadata, canonical URLs, language alternatives, structured data and sitemap settings work with the content model. The result is a deliberate publishing workflow: a page receives not only a design, but also the information that explains its purpose.
This foundation supports the work of the author and developer. Useful content still needs to answer real questions; the technical layer helps describe and connect that content consistently as the website grows.
Every page has something to say. Give it the structure to say it clearly.
One page. Several layers of meaning.
The visible headline introduces the story to the reader. SEO metadata describes it in the document head. Social metadata prepares the link for sharing. Wulver supplies these values through its SEO context so a connected template can present them together.
Name the page
An SEO title and description express the subject of a specific page. The context resolves content and site defaults, keeping metadata connected to the material being published.
Prepare the first impression
Open Graph and Twitter Card fields provide a title, description and preview image for platforms that support them. The presentation of a shared link becomes part of the publishing process.
Identify the main address
Canonical generation normalizes the page URL. Wulver supports the page parameter for pagination and omits page one, helping templates present a consistent preferred address.
The story begins before the click.
A clear title and a concise description help communicate the value of a page. The example shows the relationship between these fields; search engines may choose a different title or snippet.
Explore a Django CMS that connects design, content and the tools to develop your website.
From isolated facts to a connected story.
A website, an organization, an author and an article are different entities. Schema.org gives them a vocabulary, and JSON-LD provides a structured way to describe them. Wulver builds a Schema Graph from the available settings and content, with support for custom schemas where the project needs more control.
Site settings provide a shared starting point. Blog settings can define default schemas for categories and articles, while an individual record can supply its own schema. This gives the developer a place to express the details of the project without scattering them across unrelated templates.
Structured data should describe the content that visitors can actually see. Correct markup can make a page eligible for supported rich results, but their appearance is decided by the search engine. Wulver supplies the technical tools; the final graph still deserves validation.
Google: structured data guidelines ↗A website grows. Its routes stay connected.
Sitemap: a map with deliberate boundaries
Sitemap settings control the inclusion of the homepage, pages, categories and articles. Language versions and alternate language links can be included too. The implementation filters public content and noindex flags rather than treating every stored record as a page to publish in the map.
Languages: versions with a relationship
Wulver generates alternate language links and supports hreflang and x-default in the sitemap. These signals describe the relationship between localized addresses. Translation completeness and the final URLs remain part of the publishing review.
/old-address/301 →/new-address/A new address can preserve the path to the content.
The redirect manager supports permanent and temporary redirects. Wulver also registers localized redirects when supported page or article URLs change. After moving content, check the status and destination so readers follow a clear route to the current material.
Control what you publish. Verify what you send.
Wulver exposes robots.txt settings and noindex controls for content. These tools have different jobs: robots.txt controls crawling, while noindex asks supporting search engines not to index the page. For a crawler to read noindex, it must be able to access the page.
Google: how noindex works ↗- Review the title, description and preview image.
- Inspect canonical and alternate language URLs in the rendered HTML.
- Validate the JSON-LD graph against the actual content.
- Open the sitemap and test redirects after URL changes.
Give good content a strong foundation.
Technical SEO is ongoing care for the way a website describes itself. With Wulver, those decisions have a common home: in the content, settings and templates that shape the project. Build a useful website, give its pages clear context and keep the signals coherent as it evolves.