Three pages share the same meta description. Search engines rely on unique meta descriptions to understand each page's purpose - duplicates cause Google to ignore them and generate its own snippet, often less compelling or relevant.
Recommended action
Write a unique meta description for each of the 3 affected pages. Each should be 140–160 characters, include the target keyword, and end with a soft CTA (e.g., "Get a quote" or "Request a sample").
Sixty-two pages have very little readable text compared to their underlying code. Search engines prefer content-rich pages - this signals thin content or code-heavy templates that can depress rankings across the site.
Recommended action
Audit the 62 affected pages in SEMrush's site audit report. For each: (1) move inline CSS/JS to external files, (2) expand content on thin pages to at least 300 words of meaningful copy, (3) remove unnecessary HTML wrappers and nested div structures.
The site's robots.txt file is blocking 70 external resources from being crawled. If these include scripts, stylesheets, or fonts that help display page content, search engines may render pages incorrectly and miss important content.
Recommended action
Review robots.txt and identify which blocked external resources are used for rendering. Allow Googlebot access to render-critical third-party resources (e.g., Google Fonts, CDN-hosted CSS/JS). Use Google Search Console's URL Inspection Tool to test rendering.
One outbound link leads to a page that no longer exists. Broken links frustrate visitors and signal to search engines that the site is not well maintained.
Recommended action
Identify the broken link in SEMrush Site Audit > Issues > Warnings. Remove or replace it with a working URL pointing to a relevant, live resource.
One page links to an insecure (HTTP) destination from a secure (HTTPS) page. Browsers display security warnings for mixed content, and this can reduce visitor trust and affect rankings.
Recommended action
Find the HTTP link in SEMrush Site Audit > Warnings. Update the link to its HTTPS equivalent. If the destination doesn't support HTTPS, link to an alternative resource.
A subdomain is not enforcing HTTPS-only connections. This is a security gap that also affects trust signals - HTTPS enforcement is a confirmed Google ranking factor.
Recommended action
Add the Strict-Transport-Security header to the subdomain's server configuration: `Strict-Transport-Security: max-age=31536000; includeSubDomains`.