SEO

Most public content in Basker has an SEO tab for the editorial choices that need a human decision. Basker generates the technical foundations around that content, including canonical links, Open Graph metadata, structured data, a sitemap, and robots.txt.

For partners planning a launch or migration, SEO work falls into three areas:

• Content: clear titles, descriptions, images, and well-structured page copy.
• Discovery: indexable published content, canonical URLs, redirects, and the sitemap.
• Machine-readable context: structured data that identifies events, performances, people, venues, pages, blogs, and posts.

What you enter

The SEO tab typically holds:

• Meta title: the title used for browser tabs, search results, and link previews. Aim for around 50 to 60 characters.
• Meta description: the summary supplied to search engines and link previews. Aim for around 100 to 150 characters.
• Meta image: an optional image for Open Graph link previews.
• Canonical URL: the preferred URL when the same content can be reached at more than one address. Leave it empty to use the content's own public URL.

You can leave the meta title and meta description blank. When you do, Basker falls back to the content's own title and description. It shows that fallback as grayed-out placeholder text in the field. This lets you see what Basker will supply in the page metadata. Enter a value only when you want to override it.

These fields are translatable, so each language has its own SEO title, description, and image. See Languages and translation.

Technical SEO Basker generates

Basker adds the following to public pages:

• Open Graph metadata for link previews, including a social image when available.
• Canonical links, using the primary domain and the content's public URL unless an editor has supplied an override.
• A sitemap of published site content, including update dates.
• A robots.txt file that points crawlers to the sitemap and excludes administrative, account, and API routes. Non-public environments block crawling.

When you publish content, Basker also refreshes its site caches. Basker delivers public pages through an edge cache, while previews bypass the public cache. See Content updates and caching.

When an existing URL changes, add a redirect so visitors and search engines reach the replacement page. Redirects can point to Basker content or a custom URL, and preserve incoming query parameters. Basker can also create them automatically when a slug changes. See Redirects.

Multilingual SEO

Each enabled language has its own public URL and translated SEO fields. Pair equivalent language versions with rel="alternate" links and the correct hreflang value so search engines understand which URL serves each language. Include the current page in the set, and keep the links reciprocal. Use x-default only for a language-neutral or default landing page.

After publishing, confirm that canonical and language-alternate links point to public URLs in the intended language. See Languages and translation.

Structured data and AEO

Basker adds JSON-LD structured data to supported public content. The data uses established Schema.org types and draws from content Basker already manages:

This machine-readable context helps search engines and answer engines understand what a page represents and how related entities connect. It can also make eligible content available for richer search presentations. Each search or answer platform decides eligibility and presentation.

Good AEO content starts with the same editorial work as good SEO:

• Give each important audience question a clear page.
• Use specific headings.
• Answer the question directly.
• Keep dates, people, venues, and event details complete.

Basker's structured content and JSON-LD make those answers easier for machines to interpret. The page copy remains the source they evaluate.

For FAQ-style content, use the audience's actual question as the heading and put a direct, self-contained answer immediately below it. Keep the question and answer visible on the page, and review time-sensitive answers when the underlying content changes.

For organization identity, use the official organization name, description, and logo consistently across its Basker profile and key public pages. Keep public contact details and official profile links consistent. Reuse the organization profile when crediting producers, partners, and sponsors. These signals help search and answer platforms connect the organization with its events, people, and venues.

Auto-generating titles and descriptions

Basker can suggest a meta title or meta description from the content's own text. Use the Generate option next to either field to draft one. Review and edit the suggestion before saving: automated suggestions are a starting point, not a finished result.

For more on what these features do well and what to watch for, see AI features.

How SEO interacts with visibility

SEO metadata only affects how a piece of content appears externally if that content is published and indexable. The Show in search toggle is the single control here. It governs whether your site's own search can find the content, and whether external search engines may index it. Turn it off and Basker removes the content from its site search and sitemap. Basker also adds a noindex tag asking external search engines not to index it. A visitor with a direct link can still reach the page.

See Visibility for the full behavior of this toggle and how it interacts with navigation.

Partner launch checklist

Before launch:

• Confirm the site's primary domain. Basker uses it when generating canonical URLs.
• Review meta titles, descriptions, images, and canonical overrides in every enabled language.
• Check Show in search on each page, event, person, and post that should be discoverable.
• Add redirects for URLs kept from the previous site and for any changed Basker URLs.
• Preview important pages and check that titles, descriptions, images, dates, venues, and authors are complete.
• Publish the final content before validating the public output.

After publishing:

• Open representative pages and confirm their canonical URL and Open Graph metadata.
• On multilingual sites, confirm each public version has reciprocal language-alternate links with the correct hreflang value.
• Use a structured-data testing tool to validate one event, event instance, post, person, venue, and page.
• Open /sitemap.xml and /robots.txt on the public domain and confirm that both load.
• Test old URLs, including one with tracking parameters, and confirm that each reaches the intended destination.
• Submit the sitemap through the site's search-engine webmaster accounts and monitor indexing after launch.
• Recheck a sample of pages after major content, domain, language, or theme changes.

Where to go next