DestinX ClaimMap Guide

Customer documentation

Create a private claim library, run the first read-only audit, interpret every classification, and review the planned Pro monitoring workflow, which is coming soon.

---

1. Requirements and installation

1. Confirm WordPress 6.4 or later and PHP 7.4 or later.
2. Install DestinX ClaimMap from WordPress.org and activate it.
3. Open ClaimMap from the administration menu or select Open ClaimMap on the Plugins screen.
4. Follow the highlighted three-step Start here path.

2. Create the first claim

Field	Purpose	Example
Internal name	A private label the editorial team can recognize.	Standard delivery promise
Official text	The exact approved public wording.	Ships within 2 business days
Known variants	Accepted alternatives that remain valid.	Dispatches in 2 working days
Retired values	Wording that should now be reviewed.	Same-day dispatch
Priority	The operational importance from 1 to 5.	5 for a regulated or high-risk promise

Publish the claim before scanning. Good claims are specific promises such as a price, guarantee, service detail, delivery time, or approved positioning statement.

3. Run the first read-only scan

1. Open the Start here panel after publishing the first claim.
2. Select Start your first scan.
3. Wait for the manual scan of published posts and pages to complete.
4. Open Scan results and begin with the highest-priority Needs review matches.

4. Interpret the three classifications

Classification	Meaning	Editorial response
Consistent	The official text was found.	Verify the context if the placement is important.
Known variant	An accepted alternative was found.	Keep it or consolidate it according to the content policy.
Needs review	A retired value was found.	Open the linked editor and decide whether the wording should change.

5. Use page scopes and the Coverage Map

An optional claim scope identifies the published pages where a promise is required. The Coverage Map shows current placement and actionable required-page gaps. Scope is a planning aid; it does not add text to a page.

6. Compare Coverage History

Coverage History compares each claim with the preceding completed scan. Use it to see whether placements appeared, disappeared, or changed classification. It compares saved wording matches independently from later scope changes.

7. Review states and exports

• Verified records that an administrator reviewed the result in the current snapshot.
• Ignored records a false positive or irrelevant context in the current snapshot only.
• Open returns the current result to the working queue.
• CSV export follows the active filters and neutralizes spreadsheet-formula cells.
• The printer-friendly HTML report can be saved as PDF from the browser.

8. Planned Pro automation — coming soon

ClaimMap Pro is not yet available for purchase. It is planned to add daily or weekly local scans, completed-snapshot comparisons, a local Change Digest, an exact Alert Queue with editor links, executive reporting, and an optional plain-text administrator digest. Final scope, pricing, licensing, and release timing remain to be confirmed.

9. Privacy and content boundaries

ClaimMap stores its private claim library, scans, results, and review state in WordPress. Matching is local, deterministic, and read-only. It makes no outbound requests and contains no tracking. If the planned Pro digest ships, it will use the site mail service only after an administrator explicitly enters a valid recipient.

10. Troubleshooting checklist

Problem	Check	Action
No results	The claim may be unpublished or the wording may not exist in saved published content.	Publish the claim, verify the phrase, and run a new scan.
Expected browser-only text is missing	Free reads saved WordPress and supported local builder data, not text generated only in the browser.	Add a documented local content source or audit that interface separately.
Ignored wording returns	Ignore applies to one scan snapshot.	Review the new context and mark the new result appropriately.