Set Up Free SEO Tools in an Order You Can Verify

This checklist is for business owners, marketing managers, and freelancers who need a repeatable way to configure free SEO tooling for a single site and prove that each connection works before relying on the data.

Evidence required: identify the website being measured, who controls the domain or CMS, who can change tags or DNS, and who needs report access. If any access dependency is unknown, record it before setup begins.

Pass condition: the site owner, measurement owner, and technical owner are known, and the team can explain who is responsible for verification, configuration, and future maintenance. Fail condition: a tool is installed under an account no current owner can manage, or required access depends on an unavailable person.

Severity: missing ownership access is high because it can block verification or recovery; missing convenience access is lower until it prevents a required task. Corrective action: resolve account ownership and permissions before adding more tools. Validation: sign in with the intended account and confirm the required property or site is visible.

This route focuses on getting from no usable measurement data to a documented baseline with free tools. It is not a substitute for a broad multi-property governance process.

The setup should follow Phase 1 logic: establish ownership and access before you collect or interpret data. A report is not trustworthy merely because it contains numbers; the property, account, and scope must be the ones you intended to measure.

Evidence required: screenshots or account records showing successful verification, the selected property, user permissions, and the date the baseline was captured. Plan the first complete setup session around the source's 90-minute working example only when access is already available; treat that duration as an operating example, not a guarantee.

Pass condition: ownership is verified, collection is connected, exclusions or filters are reviewed, and a baseline is saved before material site changes. Fail condition: the team begins diagnosis while access, property scope, or collection status is still uncertain.

Severity: a setup defect that changes which site or traffic is being measured is high. A missing convenience setting is lower unless it changes the decision. Owner: assign the account owner for permissions and the site or analytics owner for implementation.

Corrective action: fix the earliest broken dependency instead of layering workarounds on top. Validation: rerun the connection check and confirm the expected property receives fresh data. Complete the related free SEO audit guide only after the foundation is stable.

If client or colleague access is pending, complete the preparatory work for steps 1-4 and mark the remaining items blocked rather than pretending the checklist has passed.

Phase 1 - Verify Ownership and Access

1. Add the site to Google Search Console. Evidence: the intended property is visible to the account owner. Pass: the property scope matches the site you intend to measure. Fail: the property excludes required variants or points at the wrong site. Severity: high. Owner: site owner or SEO owner. Corrective action: create or select the correct property. Validation: reopen Search Console and confirm access.
2. Connect Google Analytics 4 to the intended site. Evidence: the property receives test traffic from the production site. Pass: the property and site match. Fail: traffic is missing or belongs to another property. Owner: analytics owner. Corrective action: repair the connection. Validation: confirm a fresh visit appears.
3. Verify the Search Console link inside Google Analytics 4. Evidence: the expected Search Console property is available from the analytics property. Pass: the connection points to the intended site. Fail: the link is absent or points elsewhere. Owner: analytics owner. Corrective action: reconnect the properties. Validation: reopen the integration settings.
4. Confirm permissions in Google Analytics 4. Evidence: each required user can perform the assigned task. Pass: access is appropriate and recoverable. Fail: a critical account depends on an inaccessible user. Owner: property administrator. Corrective action: update access. Validation: test with the intended user.
5. Save the initial Google Analytics 4 configuration record. Evidence: the property, stream, filters, and ownership are documented. Pass: another reviewer can identify the intended measurement setup. Fail: configuration exists only in someone's memory. Owner: analytics owner. Corrective action: document the setup. Validation: compare the record with the live property.

Phase 2 - Configure the Tools

1. Submit the intended sitemap. Evidence: Search Console recognizes the submitted file. Pass: it represents URLs the site intends search engines to discover. Fail: it is inaccessible or includes unintended URLs. Owner: SEO or technical owner. Corrective action: fix the sitemap source or submission. Validation: resubmit and confirm status.
2. Review the analytics configuration in Google Analytics 4. Evidence: documented filters and measurement choices. Pass: exclusions match the team's intent. Fail: legitimate traffic is filtered or internal traffic contaminates a report used for decisions. Owner: analytics owner. Corrective action: revise the configuration. Validation: compare expected test activity with the report.
3. Confirm the Google Analytics 4 setup record before crawling. Evidence: the property and measurement scope are recorded. Pass: the setup record matches the live site. Fail: the scope is uncertain. Owner: analytics owner. Corrective action: reconcile the record. Validation: compare the saved setup with the live property.
4. Install a crawler and define scope. The source uses Screaming Frog's free tier, which supports up to 500 URLs. Evidence: the crawler can reach the production site. Pass: the selected scope covers the pages being audited. Fail: important sections are silently omitted. Owner: SEO owner. Corrective action: adjust scope or use another method for omitted areas. Validation: compare the crawl inventory with known navigation and sitemap sources.

Phase 3 - Save a Baseline

1. Run the first crawl and compare it with Google Analytics 4 landing-page evidence where useful. Evidence: a dated export of discovered URLs and response states. Pass: the crawl completes for the intended scope. Fail: missing sections are unexplained. Owner: SEO owner. Corrective action: fix scope or access, then rerun. Validation: compare the export with the expected site structure.
2. Capture Search Console performance for the last 3 months. Record the top 10 queries by clicks and the top 10 pages by impressions as the source's baseline example. Evidence: dated export. Pass: the comparison window and property are documented. Fail: screenshots exist without reproducible filters. Owner: SEO or marketing owner. Corrective action: export the report with filters recorded. Validation: another reviewer can reproduce it.
3. Record page-experience and crawl status. Evidence: affected page groups and current findings. Pass: the team knows which groups need investigation and which do not. Fail: a generic score is treated as a sitewide diagnosis. Owner: SEO and developer. Corrective action: investigate representative URLs. Validation: retest after implementation.
4. Archive the setup baseline. Save crawl and performance evidence for the later 30, 60, and 90 day comparison examples retained in the source. Treat these as review windows, not promised result dates. Pass: exports are dated and stored. Fail: the team cannot reconstruct the before-state. Owner: SEO owner. Corrective action: create the archive now. Validation: open the saved files and confirm they contain the intended property and scope.

Tool mapping prevents the team from treating every dashboard as interchangeable. The useful question is which source can provide the evidence needed for a specific decision.

• Google Search Console: use it for verified search performance, indexing evidence, manual actions, link reports, and page-experience reporting for the property. Pass when the property is verified and the relevant report contains the expected site data. Owner: SEO or site owner.
• Google Analytics 4: use it for on-site behavior and configured events. Pass when the intended property receives expected visits and the configuration is documented. Owner: analytics owner.
• Screaming Frog: use it for crawlable page-level evidence such as response codes, headings, metadata, and internal links. Pass when crawl scope is known and representative. Owner: SEO owner.
• Google PageSpeed Insights: use it to investigate specific page-performance evidence, not as a replacement for Search Console or analytics. Pass when the tested URL and reported diagnostics are recorded. Owner: developer for implementation, SEO for prioritization.
• Google Keyword Planner: use estimates as directional research evidence, not as a guarantee of organic traffic. Pass when the team records what decision the estimate is supporting and does not mix it with first-party query performance.

A common free SEO tool mistake is asking one platform to answer a question outside its lane. If two tools disagree, document the definitions and scope before deciding that one is wrong.

Validation rule: for any high-severity decision, preserve the original evidence and cross-check it with the source closest to the event being measured. A free stack is useful when it produces reproducible evidence, not because every tool shows the same number.

A setup item is done only when its evidence and validation are recorded. Use the same completion fields for every tool: evidence, pass or fail, severity if failed, owner, corrective action, and validation.

Phase 1 completion: ownership is active, required users can access the correct properties, and the team can recover the accounts.

Google Analytics 4 completion: the production property receives expected data and the configuration is documented.

Google Analytics 4 verification: the Search Console connection points to the intended property.

Google Analytics 4 access: required users can perform their assigned work without relying on an unknown account owner.

Phase 2 completion: the sitemap and crawler scope are understood, and the measurement configuration has no unexplained blocking defect.

Google Analytics 4 configuration check: filters and measurement choices match the documented intent.

Phase 3 completion: the team has a dated performance baseline, a dated crawl baseline, and at least one evidence-backed next action.

Google Analytics 4 baseline check: the saved record identifies the correct property and collection scope.

Phase 3 validation: another reviewer can open the saved evidence, identify the property and date, and reproduce the pass or fail decision.

After setup, use the baseline to choose the first corrective action. The source lists examples such as broken internal links, missing metadata, weak click-through opportunities, redirect chains, and sitemap cleanup. Treat each as a candidate that still needs evidence on your site.

• Broken responses: evidence is an internal link leading to a 4xx response or another unintended destination. Pass after the link or destination is corrected and a recrawl confirms the expected response.
• Missing titles or descriptions: evidence is the crawl export and the page's search purpose. Severity depends on page importance. Owner: content or SEO. Corrective action: write a useful, accurate element. Validation: recrawl the page.
• Low-click search queries: evidence is Search Console query and page data. Do not assume a rewrite will improve performance; compare intent, position, SERP presentation, and competing pages first. Validation is a later like-for-like performance comparison.
• Redirect chains: evidence is the exact internal path and final destination. Owner: developer or CMS owner. Corrective action: update internal links and simplify unnecessary routing where safe. Validation: recrawl the path.
• Sitemap quality: evidence is the submitted sitemap and the intended indexable URL set. Corrective action: remove unintended entries at the source. Validation: regenerate the sitemap and confirm the submitted version reflects the intended set.

The first action should be the highest-severity finding with clear evidence and a safe corrective path. If no such finding exists, keep the baseline and continue diagnosis rather than manufacturing a quick win.