← Documentation
Users and editors

Publishing, SEO, and cache

Drafts, redirects, diagnostics, and HTML caching.

Verified for version: FoxCoreCMS 1.1.1Updated: 26.09.2026

Exact states and revision history

Draft pages are unavailable publicly and excluded from menus and sitemap. Published pages become available immediately. Scheduled pages become available automatically after the specified time in the site's time zone. Each save creates a revision; the latest 50 are kept. The current state is also recorded before restoring an older one. Revisions live under storage/private/page-revisions and are included in a portable archive.

Redirect Manager

Under Settings → SEO → Redirect Manager, specify the old and new URLs, HTTP status, active state, and whether query parameters should be preserved. For an ordinary moved page, create one direct 301 from the old URL to the final new URL, without chains or loops.

Diagnostics and cache behavior

Diagnostics checks PHP, writable directories, MySQL, primary URL, HTTPS, error display, and indexing. SEO Audit finds published pages with a missing H1, title, description, or template and detects duplicate metadata. Final HTML contains one main H1: extra H1 elements from nested modules are automatically changed to H2. Dynamic blog and portfolio entries receive their own canonical and reciprocal hreflang tags; the page-header image alt text comes from the page or entry title.

Enable the file-based HTML cache in Diagnostics; its default lifetime is 300 seconds. It caches only successful GET responses. Redirects, sitemap, robots, errors, and pages containing Feedback forms are excluded. That includes forms inside a modal: the one-time token, verification question, and post-submit message must belong to the current visitor session. Changing primary JSON data updates the cache fingerprint; saving cache settings clears old files. storage/cache/html is excluded from backups.

Page states

Keep a page as a draft until its copy, translations, metadata, and links have been checked. Publication can be scheduled. Recent page revisions help recover content, but they are not a substitute for a full backup before major changes.

Redirects

When a page URL changes, redirect the old address. Permanent moves generally use 301 or 308; temporary moves use 302 or 307. Avoid redirect chains and test the final destination in every language.

Diagnostics and SEO

Before launch, check HTTPS, canonical URLs, hreflang, sitemap.xml, and robots.txt. Use the SEO audit to identify missing metadata, broken links, or unwanted duplicate URLs. Inspect real templates on mobile and measure their loading performance.

HTML cache

The file-based HTML cache speeds up repeat responses for public pages. Changes to a page or module should invalidate outdated entries automatically. If the site still shows old content, clear the cache from the administration panel. Post-submission forms and service pages must not be treated as ordinary cacheable public HTML.