A useful report helps you choose the next action. Start with a property, exact dates and a comparison period. Keep a consistent format between reviews so a new filter or an incomplete date range does not masquerade as a performance change.
Use the weekly SEO check, date comparisons and performance prompts to investigate details before writing the summary.
Prepare a weekly readout
Build a weekly SEO readout for this property using the last seven complete days and the preceding seven. State exact dates and available data.
Returns a defined reporting scope before the narrative or recommendations begin.
Show site totals and daily trends for the review period: clicks, impressions, CTR and impression-weighted average position. Identify changes worth a closer check.
Returns the overview that anchors the rest of the weekly report.
Compare pages across these two weeks. Show the largest absolute click gains and losses, both baselines and percentage changes where meaningful.
Returns the pages explaining the most visible movement in the review.
Compare queries across the same weeks. Include the biggest changes and flag small or zero earlier click baselines before describing a percentage movement.
Returns query-level evidence with safeguards against misleading percentage headlines.
Prepare a monthly investigation
Compare the last complete calendar month with the preceding month by page. State each period’s day count and flag unequal lengths when comparing totals.
Returns monthly totals with each period’s length visible in the report.
Compare these equal-length date ranges by country and device separately. Show which segments changed most and avoid adding overlapping breakdowns together.
Returns context for audience shifts without double-counting the same search traffic.
For the three pages losing the most clicks, compare query impressions, CTR and average position. Identify the next check for each page.
Returns a short investigation queue tied to specific performance evidence.
Find striking distance queries for this reporting period, sorted by impressions. Select a small review list and explain why each candidate deserves attention.
Returns potential content opportunities alongside the retrospective performance results.
Add health checks and write the summary
List Google sitemap errors and warnings for this property. Summarize what needs a file check and which questions require individual URL inspection.
Returns a discovery-health section without confusing sitemap acceptance with indexing.
For this agreed URL sample, inspect Google index status and report completed checks and outstanding URLs. State the sample scope in the report.
Returns a bounded indexing check rather than claiming full-site audit coverage.
If Bing is connected, add a Google versus Bing query comparison. State that weekly Bing data makes the compared period approximate.
Returns an optional cross-engine section with its date limitation kept explicit.
Write the final report with scope, observed changes, evidence, unknowns and three prioritized next checks. Include exact dates and do not invent causal explanations.
Returns a decision-focused report you can review and save in your own workflow.
Use the answers carefully
mowteng fetches search data live for each request and does not store reports or URL lists. Save the completed report yourself if you need a reporting history. Include the scope and comparison dates beside any exported findings so the next review can reproduce the same question and explain differences honestly.