Search and social appearance
Metadata defaults, content-type templates, approximate previews and explicit sharing overrides.
The working beta, the checks still ahead and the ideas
that may follow. No promised dates.
Native EmDash 1.3.1 is the beta launch target on Node with SQLite. Public source and release notes are available on GitHub.
Metadata defaults, content-type templates, approximate previews and explicit sharing overrides.
Built-in choices, guided entry schemas, independent library copies and website/publisher details.
Focus keywords, previews and basic browser checklists work with automatic analysis off. A manual saved-entry assessment requires a saved profile; automatic checks, history and bulk scans require explicit activation.
Indexing rules, sitemap controls, public-file configuration, redirects, verification settings and recovery tools.
Next priorities for the beta, alongside fixes reported by users.
Expand installation, upgrade, removal and recovery checks, especially on EmDash 1.3.1.
The workflow is implemented, starts off and requires activation. Public-host and provider acceptance remain unverified. No indexation result is claimed.
Cloudflare Workers/D1, Postgres and sandbox/registry installations are not yet verified. Each environment needs its own compatibility testing.
Priorities may change as people use the beta.
A guided installation path that starts with the site's hosting environment. Separate Cloudflare Free and paid-plan profiles will explain supported capabilities, defaults and optional resource use after each combination has been verified.
The beta includes custom admin names and logos. A broader white-label experience for agency and client projects is planned for 1.0.
An optional, read-only API integration for reviewing bot and AI-crawler visits in a dedicated interface. It will require explicit connection and access controls; it is not included in this beta.
A focused view of supported AI-search and crawler evidence, with coverage and limitations shown beside each result. Bot visits alone will not be presented as proof of visibility or traffic.
The guides explain what each workflow does,
what it needs and how to check its result.