Consistent SEO URLs and more polished header menus
Version 0.7.20Keep canonical URLs consistent across a site's custom and platform domains, exclude collection filters from indexing, and refine dropdown hover areas and external-link arrows.
Added
Control the external-link arrow for each header link.
Choose Auto, Show or Hide independently of the current-tab or new-tab setting. Existing links keep their default behavior until edited.
Improved
Keep collection filters out of the search index.
Valid filters, non-default sorting and non-default page sizes output noindex in server-rendered HTML. Normal pagination keeps its own canonical URL.
Make dropdown hover and focus areas consistent.
Links fill their grid cell, with shared spacing for descriptions and room for longer labels on smaller screens.
Fixed
Use one trusted canonical origin for each site.
Public SEO URLs use the site's active primary custom domain, or its platform domain when no active custom domain is configured.
Return clear responses for invalid collection URLs.
Malformed parameters return 400; nonexistent filters, empty results and out-of-range pages return 404 instead of indexable empty lists.
Resolve older cover images against the correct media domain.
Relative image references use the site's media origin in page and sharing metadata rather than being mistaken for page-domain paths.
Preserve real pages at collection-like paths.
Published block pages at paths such as /faq and /testimonials remain accessible. Policy and roadmap pages avoid duplicate page-level structured data.
Release notes
LitPage 0.7.20 improves the relationship between public URLs, search metadata and shared navigation. It also fixes dropdown highlight sizing and gives authors a separate control for external-link arrows.
Use the same preferred domain throughout SEO metadata
When a site has an active primary custom domain, its canonical URLs use that domain consistently across public pages, supported content collections and details. The corresponding sharing URLs, page identity, language links and sitemap use the same site identity.
A site without an active custom domain uses its platform domain. This does not force a new redirect or turn an unrelated domain into an alias. A temporary request failure also does not cause the canonical address to switch between domains.
Keep useful filters without indexing every variation
Visitors can continue using collection filters. Valid tag, category and release-type filters, along with non-default sorting or page sizes, now output noindex in the initial HTML.
Normal unfiltered pagination keeps a canonical URL for each page. Tracking parameters such as UTM tags are removed from canonical URLs without making an otherwise valid page noindex. Published documentation roots and articles remain eligible for indexing according to their settings.
Malformed collection parameters return 400. Nonexistent filters, empty results and out-of-range pages return 404, with a way back to the collection where supported.
These changes provide clearer signals for search engines. They do not guarantee an indexing decision, ranking change or an immediate change to Search Console reports.
Refine dropdowns and external-link indicators
Dropdown links now fill their grid cells, so hover and keyboard-focus backgrounds align more consistently when neighboring entries have different amounts of description text. Longer labels still have room to grow on smaller screens.
For each shared-header link, choose Auto, Show or Hide for the external-link arrow. This is independent of opening in a new tab. For example, a product's sign-in link can hide the arrow while links to separate tools retain it. Existing configurations keep their defaults until an author changes them.
Enabled menu links remain server-rendered.
Preserve images and existing pages
Older relative cover-image references resolve against the correct site media domain, including social sharing metadata. Published block pages at paths such as /faq and /testimonials remain accessible, and policy and roadmap pages avoid duplicate page-level structured data.
Explore the Blog, documentation center and release history to see the current published experience.