> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/seo-tools/management-dashboard/seo-analysis.md). # SEO analysis Optimising is one thing – knowing where you stand and what to do next is another. This chapter bundles the tools you use to measure the SEO health of your store and keep an eye on it. ## SEO score per product (Premium) **What is it good for?** The score sums up the SEO health of a product in a single number from 0 to 100 – based on clear criteria (meta title, description, image alt texts, canonical, schema and more). This lets you immediately spot which products need work. **How to use it:** In the SEO tab of a product you see the score as a **detail card** with a breakdown of what is good and what is missing. In the **product listing** an additional column shows the score, so you can quickly sort out problem cases. Via **Recalculate** (on the dashboard) you refresh the scores for your entire catalogue – the process runs in the background with a progress indicator. ## SEO dashboard (Premium) **What is it good for?** The dashboard is your command centre: the key metrics at a glance and a prioritised list of what to tackle next. **How to use it:** Open **SEO Tools → Dashboard**. There you see, among other things: * the **average SEO score** and the **score distribution** (how many products fall into grade A–F), * how many products are **without a meta title or description**, * the number of **noindex pages** and **active redirects**, * the **404 errors of the last 30 days**, * an **action list** with direct jumps to the matching tools. ## Image SEO check (Premium) **What is it good for?** Missing or meaningless alt texts (e.g. "IMG\_1234") hurt accessibility and image search. The scanner finds such images across the whole store and helps you improve them in one go. **How to use it:** 1. Open **SEO Tools → Image SEO** and start the **scan**. It runs in the background over all product images. 2. Afterwards you see an evaluation (images with good / missing / weak alt text) and a **paginated detail list**. 3. With the **alt text generator** you create missing alt texts automatically from a template (e.g. `{product_name} – image {position}`), either only for empty images or for all of them. ## Broken link checker (Premium) **What is it good for?** Broken links in product and category texts or in CMS content frustrate visitors and devalue you with Google. The checker crawls your content and reports which links lead nowhere. **How to use it:** Under **SEO Tools → Link check** you start the crawl. It collects the internal links from your content and checks them – **in the background** via the queue. Afterwards you see a filtered list (broken / redirect / timeout) with the status code and a suggested fix; with one click you create a redirect directly. A **weekly automatic task** keeps the check up to date. ## Google Search Console (Premium) **What is it good for?** Google Search Console shows real data: which search terms you are found for, which pages get clicked and how often, and where rankings drop. Instead of switching between Google and your store, you pull this data straight into the Administration. **How to use it:** 1. Create an OAuth credential pair in the Google Cloud Console and store the **client ID**, **client secret** and your **property URL** in the [Configuration](/en/plugins/seo-tools/configuration.md#google-search-console-premium). 2. Open **SEO Tools → Search Console** and connect your Google account (OAuth). 3. Afterwards you see your **top pages**, the **per-page performance data** and a **ranking-loss detection** that points you to pages losing visibility. A **daily sync** keeps the data up to date automatically. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.premsoft.de/en/plugins/seo-tools/management-dashboard/seo-analysis.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.