Run a global SEO check of your site combining content quality, mobile performance and basic technical SEO signals.
1. What is Site Health Audit? #
Site Health Audit is a PRO-only tool in SEO Magic that gives you a global SEO score for your site and a prioritized list of content that needs attention.
When you run an audit the plugin:
- Scans your published content (only public, non-noindex items).
- Pulls mobile performance data from Google PageSpeed Insights.
- Reads a few basic technical SEO checks from your WordPress install.
- Combines everything into:
- An Overall Site SEO Score (0–100).
- A list of “Content Requiring Attention” sorted from lowest to highest score.
Use it to decide where to work first instead of guessing.
2. How the score is calculated (high level) #
SEO Magic combines two main components:
- Average Internal Post Score (≈70% of the final score)
For each post or page, the plugin calculates an internal 0–100 score based on:- Metadata coverage (title, description and social tags filled).
- SEO plugin score from your integration (Yoast, Rank Math or AIOSEO), when available.
- Content length (short, medium, long article).
- Presence of internal links.
- Presence of external links.
- Whether the featured image has Alt text.
The average of these internal scores becomes the “Average Internal Post Score”. - Mobile PageSpeed Performance (≈30% of the final score)
Using your Google PageSpeed Insights API, SEO Magic checks your site on mobile and reads the Performance score (0–100).
The Overall Site SEO Score is a weighted combination:
- If both components are available:
70% internal content score + 30% mobile performance. - If PageSpeed data is not available, the tool falls back to internal content score only.
The score is meant to help you prioritize work, not to represent a perfect or “official” SEO grade.
3. Requirements before running an audit #
To use Site Health Audit you need:
- SEO Magic PRO license activated.
- Google API Settings configured in SEO Magic:
- A valid Google Search API Key with PageSpeed Insights enabled in your Google Cloud project.
If Google APIs are not configured or PageSpeed fails, the tool will still:
- Scan your content.
- Compute internal scores.
- Show the “Content Requiring Attention” list.
Only the PageSpeed panel and the “Mobile Performance” part of the score will be missing.
4. How to run the Site Health Audit #
- In your WordPress dashboard, go to SEO Magic → Site Health Audit.
- Click Analyze Site Health.
- A progress bar will appear showing something like:
- Processing content… (0 of 705)
- The scan runs in batches so it doesn’t overload your server.
On large sites it may take several passes; just keep the page open until the process completes. - When it finishes you will see:
- The Overall Site SEO Score.
- The PageSpeed and Technical SEO panels.
- The Content Requiring Attention table.
You can re-run the audit at any time, for example after a big round of optimizations.
5. Understanding the results #
5.1 Overall Site SEO Score #
At the top of the page you’ll see:
- A big 0–100 score labelled Overall Site SEO Score.
- A short note explaining what it’s based on (average internal score and mobile PageSpeed).
Use this as a global snapshot of your SEO health:
- 90–100 → excellent: only fine-tuning needed.
- 70–89 → good but with room for improvement.
- Below 70 → you likely have significant content or performance issues.
SEO Magic also saves the last score so you can see if things are getting better over time.

5.2 PageSpeed Insights (Mobile) #
On the left panel you’ll see a PageSpeed Insights (Mobile) block with:
- Performance score (0–100) for mobile.
- Key Core Web Vitals (LCP, FID, CLS) when available.
- Other Lighthouse category scores:
- SEO
- Accessibility
- Best Practices
- A link to view the full PageSpeed report directly in Google’s interface.
This panel helps you understand whether slow or heavy pages on mobile are pulling down your global score.

5.3 Basic Technical SEO #
On the right side, the Basic Technical SEO panel summarizes a few quick checks:
- robots.txt file – whether it exists and is reachable.
- Site indexable by search engines – based on the “Discourage search engines” setting in WordPress.
- HTTPS (SSL) enabled – whether your site is served over HTTPS.
- PHP version – useful to spot outdated versions.
- Object cache status – attempts to detect a persistent object cache (e.g. Redis, Memcached).
- PHP memory limit – the memory available to PHP for WordPress.
These values are read from your own server and WordPress configuration; SEO Magic does not change them, it only reports what it finds.

5.4 WordPress Site Health summary #
Internally, SEO Magic also runs a lightweight check using WordPress’s Site Health system.
When available, it reads:
- The number of critical issues.
- The number of recommended improvements.
- A short overall label (e.g. Good, Needs attention).
Depending on your WordPress version and setup, a brief summary may appear in the Site Health Audit view to give extra context. For detailed checks you can still go to Tools → Site Health.
5.5 Content Requiring Attention #
At the bottom of the page you’ll find a table called Content Requiring Attention.
For each item it shows:
- Title of the post or page.
- Calculated Score (0–100) – the internal score described earlier.
- A Quick Action: Edit button that sends you directly to the WordPress editor for that item.
Key details:
- The list is sorted by lowest score first, so you immediately see the weakest pages.
- Entries can include posts, pages or custom post types that are public and not marked as noindex.
- Use the Edit button, then SEO Magic’s Content Assistant, Metadata and Multimedia tools to fix the issues.
A practical workflow:
- Open the lowest-scoring items one by one in new tabs.
- Improve metadata, content structure, links and images.
- Re-run the audit later to confirm that their scores (and the global score) went up.

6. Best practices & tips #
- Run Site Health Audit regularly, especially after:
- Publishing a large batch of new content.
- Changing themes or major plugins.
- Implementing big performance or hosting changes.
- Treat the score as a compass, not a grade.
It’s designed to help you prioritize work, not to guarantee specific rankings. - If PageSpeed data is missing or you see API errors:
- Double-check your Google API key and enabled services.
- Make sure your server can reach
pagespeedonline.googleapis.com.
- On very large sites, consider:
- Running the audit during low-traffic hours.
- Increasing PHP memory/time limits if your host allows it.