Content intelligence connects information about content and its use with analysis and editorial decisions. Implementing it means making that connection usable: an editor should be able to identify the page, understand what the data covers and see who can decide the next action.
Analysis can inform that work in a spreadsheet, a reporting tool or a system that suggests changes. The useful question is how the team checks and uses the recommendation. For a shorter introduction to the term, see content intelligence. This guide focuses on setting up the working record and handoff.
Choose a decision before choosing a stack
Start with a question someone can answer and act on. “Does the preparation guide need a factual correction?” gives you a page to inspect, information to confirm and an editorial owner. “Improve all our content” leaves the necessary evidence and the next action undefined.
List the records that decision needs before comparing software. A CMS entry can identify the content and its version; a report can supply a declared observation; an information owner can confirm whether the instructions remain current. If the team cannot maintain those connections manually, identify the specific gap a tool would need to address.
Match the page, then keep the source fields
Give the editorial record a stable identifier and retain each source’s original page value alongside the mapping. Titles can change, pages can move and different versions can share similar names. Check the current destination and the known history before grouping records. Keep unresolved matches visible instead of silently assigning them to the nearest-looking title.
In Google Search Console’s Performance report, most performance data is assigned to a page’s canonical URL, rather than a duplicate URL. Keep the reported URL and check which content record it represents before joining it to another source.
The GA4 Landing page report uses the page path and query string associated with the first pageview in a session. Its dimensions are session-scoped. That field is different from a CMS identifier or a count of all views of an article. Retain the dimension’s name and its original value.
Write down the mapping rule and its exceptions. Do not remove every query string or combine language versions just because the URLs look related. A technical owner should be able to explain why the chosen records belong together and which variations remain separate.
Declare the window and the coverage
Save the source or property, report, dimension, metric, filters, start and end dates, reporting time zone and export time. An earlier export and a current view may describe different periods. Before comparing them, decide whether they cover the same interval and whether a page move or content change occurred inside it.
Search Console’s date guidance distinguishes complete and preliminary periods. Its 24-hour view uses the browser’s local time; other options show dates in Pacific Time. Record the actual view rather than assuming all reports use one time zone.
Coverage also matters. Google says some queries are anonymized and omitted, and the query table does not show every row. A saved list of queries therefore needs its scope attached. Treat it as the returned report, not a complete inventory of everything people searched.
Keep availability separate from a measured zero. Google’s export documentation says values displayed as unavailable or not a number can become zeros in downloaded data. Preserve that context when interpreting an export; it does not mean every zero is missing.
Work through a fictional preparation guide
Fictional example: Lantern Repair Workshops has a CMS record, guide-17, for its visitor preparation guide. The page has moved. A working recommendation says “rewrite the preparation guide,” but still points to an older record. The analyst has a Search Console page export and a GA4 landing-page view saved for different date windows.
| Record | What to retain | Next check |
|---|---|---|
| CMS page | The stable editorial identifier, current URL and content version | Confirm which current guide the older record refers to |
| Search Console view | The reported page, selected dates, filters and coverage notes | Check canonical attribution and the intended observation period |
| GA4 landing-page view | The original path/query value, session-scoped dimension and dates | Match the intended page and period without changing the counting unit |
| Proposed edit | The recommendation, supporting records and unresolved information | Name the person who can confirm the instructions and approve the change |
The analyst holds the rewrite while checking the mapping and the mismatched windows. The report owner can produce a comparable view or record why the comparison remains limited. The editor then reads the current guide and asks the workshop information owner to confirm the arrival instructions. That may justify a specific correction, another question or no change yet.
Give the decision a responsible owner
Separate the questions people can actually answer. The technical owner checks identifiers and report settings. The information owner confirms the organisation’s facts. The editor proposes wording and records what remains unresolved. The publishing owner approves the version to release. A small team may combine these roles while keeping each responsibility explicit.
Carry those decisions into the existing content brief or work record. Include the affected page, the source evidence, the proposed change, its owner and its review state. A person returning to the task should be able to distinguish an approved correction from a suggestion still awaiting confirmation.
Check whether the implementation works
Before expanding the arrangement, test one record from source to decision. Can a second reviewer locate the original page values, reproduce the declared report view, identify the content version and find the reason for the action? If an input is unavailable or the mapping cannot be explained, record that failure and repair the handoff.
Keep three kinds of observation separate: whether the records and settings were checked, whether an editorial change was approved and published, and what happened afterward. Choose measures that answer the decision at hand. A completed edit is an operational fact; a later change in search clicks is a different observation.
Review changes without inventing a cause
A traffic difference after an edit does not by itself show that the edit caused it. Note other changes that affect the comparison, such as a moved page, changed reporting settings or a different observation window. Keep an attributed conversion, a search visit and an observed AI response distinct when they come from different systems.
Review the record when its source, page or decision changes. Retire outdated recommendations, preserve the reason for a changed mapping and hand unresolved questions to the right owner. Use a content calendar to coordinate approved work when a publication plan is needed.
The next reviewer should be able to trace a recommendation to the relevant content, understand the evidence available at the time and see who made the decision. Build that usable path first, then assess whether an additional integration or tool improves the work.
Sources & references
Plan topics, review article drafts, and publish to a connected CMS.
Weekly local SEO teardowns
One practical email a week. Map Pack, GBP, AI Overviews. No fluff. Unsubscribe anytime.