SEO Pre Optimization Report: What to Record Before SEO Changes

Quick Answer
A report prepared before SEO optimization—often called an seo pre optimization report—records a website's condition before SEO work begins. It documents existing Google search performance, technical issues, indexed pages, content, keyword targeting, backlinks, and organic traffic. A useful report also identifies affected URLs, evidence sources, measurement dates, and recommended actions. This baseline helps website owners understand what needs attention and compare future results without confusing completed work with actual performance improvements.
Key Takeaways
- Prepare the report before changing website content, technical settings, URLs, or backlinks.
- Record Google Search Console and Google Analytics data separately because clicks and sessions measure different things.
- Include technical SEO, indexing, content, keyword targeting, internal links, and backlink information.
- Identify the affected URLs and preserve evidence for every important finding.
- Separate confirmed errors from suspected problems and improvement recommendations.
- Record the exact measurement period, tools, and collection date.
- Compare equivalent reporting periods after optimization rather than relying on isolated ranking changes.
What Is an SEO Pre Optimization Report?
An SEO pre optimization report is a dated assessment of a website before an SEO campaign or optimization project starts. It establishes the starting conditions against which future changes can be evaluated.
Imagine hiring an SEO agency to improve a business website. Before work begins, the website might already have indexing problems, outdated content, weak internal links, or pages receiving organic traffic. If nobody records those conditions, it becomes difficult to determine which problems existed before the campaign and which appeared afterward.
A baseline report addresses this problem by documenting the website's existing condition.
It also helps both parties agree on the project scope. The website owner can understand what needs attention, while the SEO provider can identify the work that should be prioritized and the information needed for future reporting.
How a Baseline Report Differs From an SEO Audit
These terms are related, but they serve different purposes.
| Document or measurement | Main purpose | Typical output |
|---|---|---|
| SEO pre-optimization report | Establish the starting condition before work | Dated baseline, existing measurements, evidence, and priorities |
| SEO audit | Investigate website problems and opportunities | Technical findings, content issues, and recommended improvements |
| SEO score | Summarize selected checks using a scoring method | A numerical score based on a particular tool's criteria |
| Monthly SEO report | Communicate progress during an ongoing campaign | Completed activities, performance trends, and outstanding work |
A baseline report may include audit findings, but its defining purpose is to preserve the original state of the website.
An SEO score is not a substitute for that evidence. Different analyzers can use different checks, scoring weights, and crawl capabilities. A high score does not establish that every important page is technically sound or performing well in Google Search.
For a closer explanation, see SEO Score Analyzer: How to Check and Interpret Your Website's SEO Score.
What Should an SEO Pre Optimization Report Include?
The report should cover the areas that can affect the website's organic search performance and the goals of the planned campaign. Not every website needs the same level of investigation, so adjust the depth according to its size, platform, and business requirements.
1. Website Scope and Reporting Conditions
Start by identifying exactly what the report covers.
Record:
- Website's canonical domain and preferred URL version.
- Relevant subdomains and important website sections.
- Main business purpose and target audience.
- Target country and language.
- Important landing pages and URL groups.
- Primary keywords and their intended destination pages.
- Reporting date and data collection period.
- Devices and locations used for performance testing, where applicable.
This information prevents confusion when the website has several domains, language versions, or different sections serving different audiences.
For example, an ecommerce website might have separate product, category, and informational pages. A report that examines only the homepage will not adequately represent the entire website.
Also document major changes already planned, such as a website migration, redesign, URL restructuring, or content replacement. These can affect later comparisons.
2. Google Search Performance
Google Search Console should be one of the main sources of baseline search data.
Its Performance report provides information such as:
- Clicks: How many times users clicked the website from Google Search results.
- Impressions: How often the website appeared in search results.
- Click-through rate (CTR): The proportion of impressions that resulted in clicks.
- Average position: The reported average position of the website's search results.
- Queries: Search terms associated with the website's appearances.
- Pages: URLs receiving search impressions and clicks.
Record the date range, property, search type, and filters used when collecting the information. Save exports where appropriate so the same measurements can be examined later.
Do not record only total clicks. Identify important pages and queries as well. A website may receive most of its search traffic from a small group of URLs, and that concentration matters when planning optimization.
Google explains the available Search Console reports and their purposes in its Search Console documentation.
3. Organic Traffic and Conversions
Search visibility is not the same as website activity.
Google Search Console measures how a website performs in Google Search. Google Analytics helps measure what visitors do after arriving on the website.
Where Analytics is correctly configured, document:
- Organic search sessions.
- Organic landing pages.
- Engaged sessions and engagement metrics.
- Configured lead submissions or purchases.
- Relevant conversion events.
- Revenue or other business outcomes, where reliable tracking exists.
Include the exact date range and the attribution or channel settings used for the report.
One important distinction: Search Console clicks and Analytics sessions are not identical measurements. A person can click a search result without generating a corresponding Analytics session, and differences in tracking, consent, processing, and measurement methods can affect the totals.
Google explains this distinction in its Search Console and Google Analytics comparison.
Never combine these figures into one metric or describe them as interchangeable.
If the website does not have reliable conversion tracking, state that limitation. An unconfigured conversion event should not be reported as zero actual conversions.
4. Indexing and Crawlability
A website can contain useful content that search engines cannot properly access or process.
The baseline should identify the indexing and crawling condition of important pages.
Check:
- Whether important URLs return successful HTTP responses.
- Whether robots.txt blocks relevant crawling.
- Whether pages contain unintended noindex directives.
- Whether canonical tags point to the intended URLs.
- Whether important pages appear in the appropriate sitemap.
- Whether redirects lead to the correct destinations.
- Whether important internal links are crawlable.
- Whether Google Search Console reports indexing problems.
Two concepts deserve particular attention:
Crawling means a search engine accesses and retrieves a page. Indexing means the page is processed and considered for inclusion in the search index.
Allowing crawling does not guarantee indexing. Similarly, a successful URL inspection does not guarantee that Google will display the page in search results.
Use the Google Search Console reports overview to understand available reports. For individual URLs, consult Google Search Console Help.
Record the exact URL and evidence for every important problem. A statement such as "some pages are not indexed" is much less useful than identifying which pages are affected and what the available evidence shows.
5. Technical SEO Condition
Technical SEO covers the website infrastructure and configuration that can affect search engine access and user experience.
Include relevant checks for:
- HTTPS configuration.
- HTTP response codes.
- Redirect chains and redirect loops.
- Broken internal links.
- Canonical URL consistency.
- Robots directives.
- XML sitemap accessibility and accuracy.
- Mobile rendering and usability.
- JavaScript-dependent content and navigation.
- Core Web Vitals and other performance observations.
For performance measurements, distinguish laboratory tests from real-user field data. Laboratory measurements are collected under controlled testing conditions. Field data reflects experiences observed from real users.
Record the testing device, location, date, and tool where relevant. Results can vary with network conditions, device capabilities, and page content.
Google's SEO Starter and maintenance documentation provides guidance on crawling, indexing, canonicalization, redirects, HTTPS, and other website fundamentals.
The Google Search Essentials documentation also explains technical requirements and search best practices. Meeting technical requirements does not guarantee crawling, indexing, or search visibility.
6. On-Page SEO and Content Quality
The report should document how important pages communicate their subjects and satisfy visitor needs.
Review:
- Page titles and meta descriptions.
- Main headings and heading structure.
- Content relevance to the intended search query.
- Missing or outdated information.
- Duplicate or substantially overlapping content.
- Image alternative text where appropriate.
- Internal links and descriptive anchor text.
- Important content that is difficult to discover.
- Pages with unclear search intent or purpose.
Avoid treating every missing keyword or tool warning as an SEO error. A page should serve its visitors, not simply contain a particular number of keywords.
For example, a service page may have a descriptive title and useful content but still need clearer information about pricing, service coverage, or the next step for prospective customers.
Record the actual weakness and its effect on the reader rather than recommending arbitrary keyword repetition.
For a broader explanation of available assessment methods, refer to Free SEO Audit: How to Check Your Website With Free Tools.
7. Keyword Targeting and URL Mapping
Document which search terms are intended to bring visitors to which pages.
A simple keyword-to-URL record can reveal:
- Important keywords without a suitable destination page.
- Multiple pages targeting substantially similar search intent.
- Pages attracting queries that do not match their purpose.
- Content gaps between the website and its intended audience.
- Pages that may need consolidation or clearer differentiation.
For example, two articles might both target the same informational question. Before creating another article, examine whether improving or consolidating the existing content would better serve the reader.
A useful internal reference is Search Engine Mapping: How to Match Keywords to the Right Pages.
The baseline should preserve the original keyword-to-URL assignments so that future changes can be evaluated against the starting structure.
8. Backlink Profile
Backlinks are links from other websites pointing to your website. They can provide useful information about external references and link acquisition, but third-party backlink reports are estimates rather than complete records of every link on the web.
Depending on the campaign, record:
- Total referring domains reported by the selected tool.
- Total backlinks reported by that tool.
- Important linking pages.
- Relevant anchor text patterns.
- Links pointing to important landing pages.
- Potentially suspicious or irrelevant link patterns.
- Collection date and tool name.
A referring domain is a unique website linking to the target website. It is different from the total number of backlinks because one domain can provide multiple links.
Do not compare backlink totals from different providers as though they were collected using identical databases and methods. Record the provider and date for every measurement.
Also distinguish existing backlinks from links acquired during the new campaign. Otherwise, subsequent reporting can misrepresent what the SEO provider actually delivered.
A Practical SEO Pre Optimization Report Template
A good report should make findings easy to verify and easy to revisit. The following matrix can be adapted for a small business website, an ecommerce store, or a larger organization.
| Report category | What to record | Evidence source | Verification status | Priority | Recommended action | Later comparison |
|---|---|---|---|---|---|---|
| Website scope | Domain, URL groups, target country, and reporting date | Project records and website configuration | Confirmed or incomplete | Based on project scope | Complete the agreed scope | Changes to scope or structure |
| Search performance | Clicks, impressions, CTR, queries, and average position | Google Search Console | Measured | Based on business importance | Investigate relevant trends | Equivalent search performance measurements |
| Organic traffic | Sessions, landing pages, and configured conversions | Google Analytics | Measured or tracking unavailable | Based on business importance | Verify tracking or investigate trends | Equivalent traffic and conversion measurements |
| Indexing | Important indexed and excluded URLs | Search Console and URL inspection | Confirmed, suspected, or unverified | Based on URL importance | Investigate and correct verified issues | Changes in the status of important URLs |
| Technical SEO | Response codes, redirects, canonical tags, and robots directives | Crawler and browser checks | Confirmed or requires verification | Based on impact and affected pages | Repair verified defects | Verified corrections and new issues |
| Content | Titles, headings, relevance, and outdated information | Page inspection | Observed or recommended | Based on reader and business value | Improve identified content | Content changes and resulting observations |
| Keyword targeting | Target keywords and assigned URLs | Keyword research and mapping records | Confirmed or under review | Based on strategic importance | Resolve gaps or competing intent | Changes in keyword-to-URL assignments |
| Internal links | Important linking pages and destinations | Website crawler and manual inspection | Confirmed or requires verification | Based on page importance | Repair or improve relevant links | New, removed, or repaired links |
| Backlinks | Referring domains and backlinks reported by a named provider | Backlink platform | Tool-reported estimate | Based on relevance and risk | Investigate relevant patterns | Measurements from the same provider where possible |
| Performance | Laboratory and field performance observations | Performance testing tools | Measured under stated conditions | Based on user impact | Investigate significant problems | Comparable device and testing conditions |
For every significant issue, preserve the exact affected URL, observed condition, evidence or screenshot reference, collection date, verification status, priority and reason, recommended action, responsible person or team, and completion status.
This turns the report into a practical working record rather than a collection of disconnected audit scores.
Example: Recording a Technical Problem Correctly
The following example is hypothetical and demonstrates how to classify findings. It is not a real client result.
Imagine that an important service page contains an unintended noindex directive.
| Field | Example entry |
|---|---|
| Category | Indexing |
| Affected URL | /services/example/ |
| Observed condition | A noindex directive is present |
| Evidence | Retrieved page HTML and URL inspection |
| Verification status | Confirmed, if the available checks support the finding |
| Priority | High, because the page is an important business destination |
| Recommended action | Investigate the directive and remove it if unintended |
| Later comparison | Verify the directive's removal and review indexing status |
Now compare that with a recommendation to improve the page title.
A title recommendation is not automatically a technical error. It should be recorded as an optimization opportunity, with its reason and proposed change, rather than being presented as an existing defect.
This distinction matters because website owners need to know which problems already exist and which changes are being proposed by the SEO team.
How to Compare the Baseline After SEO Optimization
The original report should remain unchanged as the historical starting point. Create a separate follow-up report when optimization work has been completed or when the agreed reporting period arrives.
Use a consistent comparison process.
1. Compare equivalent periods. Use suitable date ranges and account for seasonal changes. A holiday shopping period should not automatically be compared with a quiet period as though demand were constant.
2. Keep the same data sources. Compare Google Search Console with Google Search Console and Analytics with Analytics. Avoid switching providers or measurement methods without documenting the difference.
3. Review the same pages and queries. Changes in website structure can make total-site comparisons misleading. Keep important URL groups identifiable.
4. Separate activities from outcomes. Publishing an article, repairing a redirect, or acquiring a backlink is completed work. Increased impressions, clicks, or conversions are measured outcomes. One does not automatically prove the other caused the result.
5. Document unexpected changes. Record migrations, tracking updates, site outages, major content changes, and other events that may influence the comparison.
6. Verify completed technical fixes. If the initial report identified a broken URL or unintended directive, check the actual page again rather than assuming the problem has been resolved because someone marked the task complete.
A meaningful comparison should answer three separate questions:
- What work was completed?
- What changed in the website's technical and content condition?
- What happened to search performance and business outcomes over the comparison period?
Keeping these questions separate produces a more credible account of campaign performance.
Common Mistakes That Make Baseline Reports Misleading
Even a detailed report can be unreliable when its measurements and findings are not clearly explained.
Using One SEO Score as the Entire Report
A single number cannot adequately describe search performance, technical accessibility, content quality, indexing, and business results. Keep the underlying observations and evidence.
Forgetting the Measurement Period
A performance number without a date range has limited value. Always identify when the data was collected and which period it represents.
Mixing Different Analytics Measurements
Search Console clicks and Analytics sessions are not interchangeable. Keep them separate and explain their sources.
Reporting Tool Warnings as Confirmed Errors
Automated tools can flag possible problems that require manual verification. Label uncertain findings clearly instead of presenting every warning as a confirmed defect.
Ignoring Important Website Sections
A homepage-only assessment may miss serious issues affecting product pages, service pages, or important articles. Define the report's coverage before drawing conclusions.
Failing to Preserve Original Evidence
If the website changes before the baseline is saved, the original condition may be difficult to reconstruct. Preserve exports, screenshots, and relevant technical observations before implementation.
Promising Guaranteed Ranking Improvements
A baseline report improves planning and accountability. It cannot guarantee that Google will index a particular URL, improve a ranking, or deliver a specific amount of organic traffic.
Frequently Asked Questions
What Is the Purpose of an SEO Pre Optimization Report?
Its purpose is to document a website's existing SEO condition before changes begin. It provides a starting point for prioritizing work, agreeing on project scope, and evaluating later measurements.
When Should an SEO Pre Optimization Report Be Prepared?
Prepare it before implementing technical changes, publishing major content updates, restructuring URLs, starting a backlink campaign, or beginning a new SEO engagement. Preserve the original measurements before work starts.
Is an SEO Pre Optimization Report the Same as an SEO Audit?
No. An SEO audit investigates website problems and opportunities. A pre-optimization report documents the starting condition and preserves the evidence needed for later comparison. The two can be part of the same project.
Which Tools Are Needed to Prepare an SEO Pre Optimization Report?
Google Search Console is useful for search visibility and indexing information. Google Analytics can provide website traffic and conversion measurements when properly configured. Technical crawlers, browser inspections, and backlink platforms can provide additional evidence. The appropriate combination depends on the website and reporting scope.
How Long Should the Baseline Reporting Period Be?
There is no single period suitable for every website. Choose a period that provides enough useful data while considering traffic volume, seasonality, and the project's goals. Record the exact start and end dates so later comparisons remain transparent.
Should Backlinks Be Included in the Report?
Yes, when backlink condition or link acquisition is relevant to the planned campaign. Record the provider, collection date, referring domains, and important linking pages. Remember that third-party backlink indexes are estimates rather than complete records.
Does a Good Baseline Report Guarantee Better Google Rankings?
No. A baseline report helps identify existing conditions and measure subsequent changes. Search rankings depend on many factors, and neither a report nor an optimization plan can guarantee a particular Google ranking or indexing outcome.
Final Thoughts
An effective SEO pre optimization report gives website owners something more valuable than a score: a clear, dated record of where the website stands before work begins.
The most useful report connects each important observation to an affected URL, an evidence source, a measurement period, and a practical next step. It also preserves the original data so future reporting can distinguish completed SEO activities from actual changes in search performance.
Whether you are preparing your own website or evaluating an SEO agency, insist on a documented baseline before optimization starts. It creates a clearer agreement about the work, makes reporting easier to verify, and provides a more reliable foundation for future decisions.