The citelayer® Dashboard
Use the dashboard to move from a status summary to the actual response or local data behind it. A green card is useful only within the feature it checks.
Integration and Troubleshooting
Use verified hooks and REST contracts, check SEO output ownership, and troubleshoot collection or response problems on your actual WordPress setup.
9 articles
Markdown Scope, Archives and Exclusions
Markdown output depends on both an explicit Markdown request and the content scope selected in citelayer®. Use exclusions for content that should stay outside this surface.
SEO Plugin Compatibility and Output Ownership
citelayer® detects supported SEO providers so you can keep ownership of existing output clear. Provider detection and emitted markup are separate things.
Caching and Accurate AI Activity Logs
A full-page cache or CDN can serve a response before WordPress runs. That matters for both current content and completeness of local crawler logs.
Developer Hooks and Filters
Use the hooks implemented in the installed release and keep output factual. This reference covers a small verified set rather than hypothetical integration names.
REST API and Commerce Integration Reference
Discover the routes registered on your site, then use the contract for the active component. Read-only checks and order-creating requests have very different effects.
Export Crawler Logs as CSV
Export the locally collected crawler records for a chosen analysis. Keep the file private when it includes optional IP information or sensitive URL paths.
Crawler Logs: Inspect Matching Requests
Crawler Logs shows the request records collected inside WordPress. It is the detail view behind the bot dashboard, useful for investigating paths and changes.
Frequently Asked Questions
Answers to common setup questions, with the limits that matter when interpreting the results.