Skip to content

Published · Updated

Choose a question before choosing a dashboard

A useful monthly report answers whether people can discover your church and take a meaningful next step. It should not turn every click into a claim of attendance growth. Start with three questions: which searches bring people to the site, which pages help them, and which useful actions are completed?

1. Establish a comparable baseline

In Search Console, record the property, date range, impressions, clicks, click-through rate and important pages or queries. Compare similar periods and note major holidays, campaigns or venue changes. Average position summarizes reported search appearances; it is not a universal ranking for every person or a Google Maps position.

2. Define a completed action precisely

Choose a small set of useful actions, such as a delivered visit inquiry or completed event registration. A button click is a start, not proof of completion. Document the trigger, destination, owner and exclusions. Keep donation or payment reporting separate from attendance and never use sensitive pastoral details as analytics parameters.

3. Test the route across website boundaries

If registration or another task continues in a separate app, test the actual link with a harmless campaign label. Check that analytics uses the intended property, preserves appropriate attribution and records one completed action. Verify consent before tracking and check that rejection remains respected after navigation.

4. Keep technical scores in their proper role

A mobile Lighthouse test is a simulated measurement. Real-user Core Web Vitals require field data; a lack of data is not a pass or failure. Record the URL, date and test context. Treat a useful technical fix as a better experience, not proof of a search-ranking or attendance increase.

5. Use this monthly report format

Period and comparison: [dates]. Search visibility: [impressions, clicks and relevant pages]. Useful actions: [verified completions and definitions]. Changes: [dated edits]. Limits: [missing data or seasonal context]. Next actions: [owner and review date]. Keep original exports so a future review can check the interpretation.

A decision example, not a performance claim

Suppose impressions increase but completed visit inquiries do not. First confirm comparable periods, working forms and accurate event definitions. Then review whether the landing page answers arrival questions. Do not immediately attribute the difference to content quality or assume more people attended. Use the evidence to select one next test.

Sources and further reading