"Issue Name","Issue Type","Issue Priority","URLs","% of Total","Description","How To Fix","Help URL" "Security: Missing HSTS Header","Warning","Low","1","0.000","URLs that are missing the HSTS response header. The HTTP Strict-Transport-Security response header (HSTS) instructs browsers that it should only be accessed using HTTPS, rather than HTTP. If a website accepts a connection to HTTP, before being redirected to HTTPS, visitors will initially still communicate over HTTP. The HSTS header instructs the browser to never load over HTTP and to automatically convert all requests to HTTPS.","The HSTS header should be used across all pages to instruct the browser that it should always request pages via HTTPS, rather than HTTP.","" "JavaScript: Page Title Updated by JavaScript","Warning","Medium","122","0.520","Pages that have page titles that are modified by JavaScript. This means the page title in the raw HTML is different to the page title in the rendered HTML.","While Google is able to render pages and see client-side only content, consider including important content server side in the raw HTML.","" "Structured Data: Parse Errors","Issue","High","588","2.490","URLs which have structured data that failed to parse correctly. This is often due to incorrect mark-up in the structured data, which might impact search engines' ability to interpret it reliably.","Review and resolve any issues in the structured data markup, so that they can be parsed reliably. Debug parsing errors using the JSON-LD Playground tool or Schema Markup Validator.","" "Canonicals: Missing","Warning","Medium","6","0.030","Pages that have no canonical URL present either as a link element, or via HTTP header. If a page doesn't indicate a canonical URL, Google will identify what they think is the best version or URL. This can lead to ranking unpredictability when there are multiple versions discovered, and hence generally all URLs should specify a canonical version","Specify a canonical URL for every page to avoid any potential ranking unpredictability if multiple versions of the same page are discovered on different URLs.","" "Security: Missing Content-Security-Policy Header","Warning","Low","23892","44.260","URLs that are missing the Content-Security-Policy response header. This header allows a website to control which resources are loaded for a page. This policy can help guard against cross-site scripting (XSS) attacks that exploit the browser's trust of the content received from the server. The SEO Spider only checks for existence of the header, and does not interrogate the policies found within the header to determine whether they are well set-up for the website. This should be performed manually.","Set a strict Content-Security-Policy response header across all page to help mitigate cross site scripting (XSS) and data injection attacks.","" "Response Codes: Internal Blocked Resource","Warning","High","21268","35.730","Internal resources (such as images, JavaScript and CSS) that are blocked from rendering by robots.txt or an error. This filter will only populate when JavaScript rendering is enabled (blocked resources will appear under 'Blocked by Robots.txt' in default 'text only' crawl mode). This can be an issue as the search engines might not be able to access critical resources to be able to render pages accurately. Blocked resources can be viewed by URL in the 'Rendered Page' tab, and any pages with blocked resources can be viewed under 'JavaScript > Pages with Blocked Resources'.","Update the robots.txt and resolve any errors to allow all critical resources to be crawled and used for rendering of website content.","" "Meta Description: Over 155 Characters","Opportunity","Low","6953","29.400","Pages which have meta descriptions over the configured limit. Characters over this limit might be truncated in Google's search results.","Write concise meta descriptions to ensure important words are not truncated in the search results, and not visible to users.","" "Security: Missing X-Frame-Options Header","Warning","Low","23846","44.170","URLs missing an X-Frame-Options response header with a 'DENY' or 'SAMEORIGIN' value. This instructs the browser not to render a page within a frame, iframe, embed or object. This helps avoid 'clickjacking' attacks, where your content is displayed on another web page that is controlled by an attacker.","To minimise security issues, the X-Frame-Options response header should be supplied with a 'DENY' or 'SAMEORIGIN' value.","" "H1: Over 70 Characters","Opportunity","Low","851","3.600","Pages which have