"Issue Name","Issue Type","Issue Priority","URLs","% of Total","Description","How To Fix","Help URL"
"Response Codes: Internal Client Error (4xx)","Issue","High","21","0.080","Internal URLs with a client-side error. This indicates a problem occurred with the URL request and can include responses such as 400 bad request, 403 Forbidden, 404 Page Not Found, 410 Removed, 429 Too Many Requests and more. A 404 'Page Not Found' is the most common, and often referred to as a broken link. View URLs that link to errors using the lower 'inlinks' tab and export them in bulk via 'Bulk Export > Response Codes > Internal > Client Error (4xx) inlinks'.","All links on a website should ideally resolve to 200 'OK' URLs. Errors such as a 404 or 410 should be updated to their correct locations, removed and redirected where appropriate. A 403 forbidden error occurs when a web server denies access to the SEO Spider's request and can often be resolved by switching the user-agent to Chrome via 'Config > User-Agent' and crawling again.",""
"JavaScript: Page Title Updated by JavaScript","Warning","Medium","1187","11.780","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.",""
"H1: Duplicate","Opportunity","Low","122","1.210","Pages which have duplicate <h1>s. It's important to have distinct, unique and useful main headings. If every page has the same <h1>, then it can make it more challenging for users and the search engines to understand one page from another.","Update duplicate <h1>s as necessary, so important pages contain a unique and descriptive <h1> for users and search engines.  If these are duplicate pages, then fix the duplicated pages by linking to a single version, and redirect or use canonicals where appropriate.",""
"Links: Internal Outlinks With No Anchor Text","Opportunity","Low","10079","100.000","Pages that have internal links without anchor text or images that are hyperlinked without alt text. Anchor text is the visible text and words used in hyperlinks that provide users and search engines context about the content of the target page. Internal outlinks without anchor text can be seen in the 'Outlinks' tab, with the 'All Link Types' filter set to 'Hyperlinks', where the 'Anchor Text' column is blank, or if an image, the 'Alt Text' column is also blank. Export in bulk via 'Bulk Export > Links > Internal Outlinks With No Anchor Text'.","Review the missing anchor text outlinks and where appropriate include useful and descriptive anchor text to help users and search engines.",""
"URL: Over 115 Characters","Opportunity","Low","259","1.330","URLs that are more than the configured length. This is generally not an issue, however research has shown that users prefer shorter, concise URL strings.","Where possible use logical and concise URLs for users and search engines. However, changing URLs is a big decision, and often it's not worth changing them for SEO purposes alone. If URLs are changed, then appropriate 301 redirects must be implemented.",""
"Response Codes: External No Response","Warning","Low","161","0.590","External URLs with no response returned from the server. Usually due to a malformed URL, connection timeout, connection error, or connection refused. View URLs that link to no responses using the lower 'inlinks' tab and export them in bulk via 'Bulk Export > Response Codes > External > No Response inlinks'.","Malformed URLs should be updated to the correct location and other connection issues can often be resolved by using different user-agents ('Config > User-Agent'), adjusting the crawl speed ('Config > Speed') or disabling firewalls & proxies. If they can be viewed in a browser, then it's often not an issue.",""
"Meta Description: Duplicate","Opportunity","Low","72","0.710","Pages which have duplicate meta descriptions. It's really important to have distinct and unique meta descriptions that communicate the benefits and purpose of each page. If they are duplicate or irrelevant, then they will be ignored by search engines in their snippets.","Update duplicate meta descriptions as necessary, so important pages contain a unique and descriptive title for users and search engines. If these are duplicate pages, then fix the duplicated pages by linking to a single version, and redirect or use canonicals where appropriate.",""
"Canonicals: Non-Indexable Canonical","Issue","High","9","0.090","Pages with a canonical URL that is non-indexable. This will include canonicals which are blocked by robots.txt, no response, redirect (3XX), client error (4XX), server error (5XX), are 'noindex' or 'canonicalised' themselves. This means the search engines are being instructed to consolidate indexing and link signals to a non-indexable page, which often leads to them ignoring the canonical, but may also lead to unpredictability in indexing and ranking. Export pages, their canonicals and status codes via 'Reports > Canonicals > Non-Indexable Canonicals'.","Ensure canonical URLs are to accurate indexable pages to avoid them being ignored by search engines, and any potential indexing or ranking unpredictability.",""
"Response Codes: Internal Redirection (3xx)","Warning","Low","185","0.680","Internal URLs which redirect to another URL. These will include server-side redirects, such as 301 or 302 redirects (and more). View URLs that link to redirects using the lower 'inlinks' tab and export them in bulk via 'Bulk Export > Response Codes > Internal > Redirection (3xx) inlinks'.","Ideally all internal links would be to canonical resolving URLs, and avoid linking to URLs that redirect. This reduces latency of redirect hops for users, and enhanced efficiency for search engines.",""
"Security: Missing Secure Referrer-Policy Header","Warning","Low","10201","52.270","URLs missing 'no-referrer-when-downgrade', 'strict-origin-when-cross-origin', 'no-referrer' or 'strict-origin' policies in the Referrer-Policy header. When using HTTPS, it's important that the URLs do not leak in non-HTTPS requests. This can expose users to 'man in the middle' attacks, as anyone on the network can view them.","Consider setting a referrer policy of strict-origin-when-cross-origin. It retains much of the referrer's usefulness, while mitigating the risk of leaking data cross-origins.",""
"Validation: High Carbon Rating","Opportunity","Low","2","0.010","URLs that have a carbon rating of F using the digital carbon ratings system from Sustainable Web Design. This scale equates page weight tracked by the HTTP Archive with CO2 estimates per page view. The CO2 calculation uses the 'The Sustainable Web Design Model' for calculating emissions, which considers datacentres, network transfer and device usage in calculations. The CO2 calculation and rating system can be used as a benchmark, as well as a catalyst to contribute to a more sustainable web.","Consider optimisation opportunities to reduce file size and CO2 emissions, and improve carbon footprint and rating. The CO2 calculation and carbon rating can be integrated with analytics data to help prioritise which areas or URLs should be focused upon. Review best practices and opportunities listed under the PageSpeed tab for more specific actions.",""
"Response Codes: External Server Error (5xx)","Warning","Low","24","0.090","External URLs where the server failed to fulfill an apparently valid request. This can include common responses such as 500 Internal Server Errors and 503 Service Unavailable. View URLs that link to errors using the lower 'inlinks' tab and export them in bulk via 'Bulk Export > Response Codes > External > Server Error (5xx) inlinks'.","All URLs should respond with a 200 'OK' status and this might indicate a server that struggles under load, or a misconfiguration that requires investigation. If they can be viewed in a browser, then it's often not an issue.",""
"Page Titles: Below 30 Characters","Opportunity","Medium","984","9.760","Pages which have page titles under the configured limit. This isn't necessarily an issue, but it does indicate there might be room to target additional keywords or communicate your USPs.","Consider updating the page title to take advantage of the space left to include additional target keywords or USPs.",""
"H1: Missing","Issue","Medium","16","0.160","Pages which have a missing <h1>, the content is empty or has a whitespace. The <h1> should describe the main title and purpose of the page and are considered to be one of the stronger on-page ranking signals.","Ensure important pages have concise, descriptive and unique headings to help users, and enable search engines to score and rank the page for relevant search queries.",""
"Meta Description: Missing","Opportunity","Low","470","4.660","Pages which have a missing meta description, the content is empty or has a whitespace. This is a missed opportunity to communicate the benefits of your product or service and influence click through rates for important URLs.","It's important to write unique and descriptive meta descriptions on key pages to communicate the purpose of the page to users, and entice them to click on your result over the competition. It can also mean Google use this description for snippets in the search results for some queries, rather than make up their own based upon the content of the page.",""
"Structured Data: Rich Result Validation Warnings","Opportunity","Low","5366","53.240","URLs that contain Google rich result feature validation warnings. These will always be for 'recommended properties', rather than required properties. Recommended properties can be included to add more information about content which could provide a better user experience, but they do not disqualify you from being eligible for rich snippets.","Consider warnings as 'opportunities' to improve the data provided to search engines and users to potentially enhance special search result features in Google. Review the 'Structured Data Details' tab for more information on specific warnings and refer to Google rich result feature docs where necessary. Export unique validation errors using 'Reports > Structured Data > Validation Errors & Warnings Summary'.",""
"H1: Over 70 Characters","Opportunity","Low","720","7.140","Pages which have <h1>s over the configured length. There is no hard limit for characters in an <h1>, however they should be clear and concise for users and long headings might be less helpful","Write concise <h1>s for users, including target keywords where natural for users - without keyword stuffing.",""
"URL: Contains Space","Issue","Low","2","0.010","URLs that contain a space. These are considered unsafe and could cause the link to be broken when sharing the URL. Hyphens should be used as word separators instead of spaces.","Ideally hyphens should be used as word separators, rather than spaces. However, changing URLs is a big decision. If URLs are changed, then appropriate 301 redirects must be implemented.",""
"H2: Multiple","Warning","Low","361","3.580","Pages which have multiple <h2>s. This is not an issue as HTML standards allow multiple <h2>'s when used in a logical hierarchical heading structure. However, this filter can help you quickly scan to review if they are used appropriately.","Ensure <h2>s are used in a logical hierarchical heading structure, and update where appropriate utilising the full heading rank between (h3 - h6) for additional headings.",""
"Links: Internal Nofollow Outlinks","Warning","Low","19","0.190","Pages that use rel=""nofollow"" on internal outlinks. Links with nofollow link attributes will generally not be followed by search engines. Remember that the linked pages may be found through other means, such as other followed links, or XML Sitemaps etc. Nofollow outlinks can be seen in the 'Outlinks' tab with the 'All Link Types' filter set to 'Hyperlinks', where the 'Follow' column is 'False'. Export in bulk via 'Bulk Export > Links > Internal Nofollow Outlinks'.","Review the use of rel=""nofollow"" on internal links. These might be valid to URLs that ideally wouldn't be crawled, or they could be by mistake. Remove the nofollow link attribute to important URLs you wish to be crawled, indexed and receive PageRank.",""
"H2: Over 70 Characters","Opportunity","Low","3949","39.180","Pages which have <h2>s over the configured limit. There is no hard limit for characters in an <h2>, however they should be clear and concise for users and long headings might be less helpful","Write concise <h2>s for users, including target keywords where natural for users - without keyword stuffing.",""
"Response Codes: Internal Blocked by Robots.txt","Warning","High","9110","33.600","Internal URLs blocked by the site's robots.txt. This means they cannot be crawled and is a critical issue if you want the page content to be crawled and indexed by search engines. View URLs that link to URLs blocked by robots.txt using the lower 'inlinks' tab and export them in bulk via 'Bulk Export > Response Codes > Internal > Blocked by Robots.txt inlinks'.","Review URLs to ensure they should be disallowed. If they are incorrectly disallowed, then the site's robots.txt should be updated to allow them to be crawled. Consider whether you should be linking internally to these URLs and remove links where appropriate.",""
"H2: Missing","Warning","Low","51","0.510","Pages which have a missing <h2>, the content is empty or has a whitespace. The <h2> heading is often used to describe sections or topics within a document. They act as signposts for the user, and can help search engines understand the page.","Consider using logical and descriptive <h2>s on important pages that help the user and search engines better understand the page.",""
"Directives: Nofollow","Warning","High","6","0.060","URLs containing a 'nofollow' directive in either a robots meta tag or X-Robots-Tag in the HTTP header. This is a 'hint' which tells the search engines not to follow any links on the page for crawling. This is generally used by mistake in combination with 'noindex', when there is no need to include this directive as it stops 'PageRank' from being passed onwards. To crawl pages with a nofollow directive within the SEO Spider, enable 'Follow Internal Nofollow' via 'Config > Spider'.","URLs with a 'nofollow' should be reviewed carefully to ensure that links shouldn't be crawled and PageRank shouldn't be passed on. If outlinks should be crawled and PageRank should be passed onwards, then the 'nofollow' directive should be removed.",""
"Page Titles: Below 200 Pixels","Opportunity","Medium","312","3.100","Pages which have page titles much shorter than Google's estimated pixel length limit. This isn't necessarily an issue, but it does indicate there might be room to target additional keywords or communicate your USPs.","Consider updating the page title to take advantage of the space left to include additional target keywords or USPs.",""
"Meta Description: Over 155 Characters","Opportunity","Low","2865","28.430","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.",""
"URL: GA Tracking Parameters","Warning","Low","3","0.020","URLs that contain Google Analytics tracking parameters. In addition to creating duplicate pages that must be crawled, using tracking parameters on links internally can overwrite the original session data. utm= parameters strip the original source of traffic and starts a new session with the specified attributes. _ga= and _gl= parameters are used for cross-domain linking and identify a specific user, including this on links prevents a unique user ID from being assigned.","Remove the tracking parameters from links. Event Tracking is recommended in place of utm parameters for tracking additional interactions on a page such as downloads, link clicks, form submissions, and video plays.",""
"H2: Duplicate","Opportunity","Low","108","1.070","Pages which have duplicate <h2>s. It's important to have distinct, unique and useful pages. If every page has the same <h2>, then it can make it more challenging for users and the search engines to understand one page from another.","Update duplicate <h2>s as necessary, so important pages contain a unique and descriptive <h2> for users and search engines.  If these are duplicate pages, then fix the duplicated pages by linking to a single version, and redirect or use canonicals where appropriate.",""
"Response Codes: External Client Error (4xx)","Warning","Low","1557","5.740","External URLs with a client-side error. This indicates a problem occurred with the URL request and can include responses such as 400 bad request, 403 Forbidden, 404 Page Not Found, 410 Removed, 429 Too Many Requests and more. A 404 'Page Not Found' is the most common, and often referred to as a broken link. View URLs that link to errors using the lower 'inlinks' tab and export them in bulk via 'Bulk Export > Response Codes > External > Client Error (4xx) inlinks'.","All links on a website should ideally resolve to 200 'OK' URLs. Errors such as 404 broken links should be updated so users are taken to the correct URL, or removed. A 403 forbidden error occurs when a web server denies access to the SEO Spider's request and can often be resolved by switching the user-agent to Chrome via 'Config > User-Agent'. If they can be viewed in a browser, then it's often not an issue.",""
"Canonicals: Contains Fragment URL","Issue","High","1","0.010","Pages with a rel=""canonical"" that includes a fragment URL in the href attribute. Google generally doesn't support fragment URLs. These annotations are ignored and not used for canonicalisation by Google.","Remove fragment URLs from canonical annotations and ensure they are to accurate indexable pages to avoid them being ignored by search engines, and any potential indexing or ranking unpredictability.",""
"Security: Missing HSTS Header","Warning","Low","1","0.010","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.",""
"Response Codes: Internal Blocked Resource","Warning","High","8508","31.380","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.",""
"Page Titles: Over 561 Pixels","Opportunity","Medium","1556","15.440","Pages which have page titles over Google's estimated pixel length limit for titles in search results. Google snippet length is actually based upon pixels limits, rather than a character length. The SEO Spider tries to match the latest pixel truncation points in the SERPs, but it is an approximation and Google adjusts them frequently.","Write concise page titles to ensure important words are not truncated in the search results, not visible to users and potentially weighted less in scoring.",""
"Canonicals: Canonicalised","Warning","High","725","7.190","Pages that have a canonical to a different URL. The URL is 'canonicalised' to another location. This means the search engines are being instructed to not index the page, and the indexing and linking properties should be consolidated to the URL in the canonical.","These URLs should be reviewed carefully to ensure the indexing and link signals are being consolidated to the correct URL. In a perfect world, a website wouldn't need to canonicalise any URLs as only canonical versions would be linked to internally on a website, but often they are required due to various circumstances outside of control, and to prevent duplicate content. Update internal links to canonical versions of URLs where possible.",""
"Security: Unsafe Cross-Origin Links","Warning","Low","1847","9.460","URLs that link to external websites using the target=""_blank"" attribute (to open in a new tab), without using rel=""noopener"" (or rel=""noreferrer"") at the same time. Using target=""_blank"" alone leaves those pages exposed to both security and performance issues for some legacy browsers, which are estimated to be below 5% of market share. Setting target=""_blank"" on <a> elements implicitly provides the same rel behavior as setting rel=""noopener"" which does not set window.opener for most modern browsers, such as Chrome, Safari, Firefox and Edge.  The external links that contain the target=""_blank"" attribute by itself can be viewed in the 'outlinks' tab and 'target' column. They can be exported alongside the pages they are linked from via 'Bulk Export > Security > Unsafe Cross-Origin Links'.","Consider the benefits of including the rel=""noopener"" link attribute on any links that contain the target=""_blank"" attribute to avoid security and performance issues for the users of legacy browsers that may visit the website.",""
"JavaScript: Contains JavaScript Links","Warning","Medium","1007","9.990","Pages that contain hyperlinks that are only discovered in the rendered HTML after JavaScript execution. These hyperlinks are not in the raw HTML.","While Google is able to render pages and see client-side only links, consider including important links server side in the raw HTML.",""
"Structured Data: Rich Result Validation Errors","Issue","High","1054","10.460","URLs that contain Google rich result feature validation errors. Google rich result feature validation will show errors for missing required properties or problems with the implementation of required properties. Google's 'required properties' must be included and be valid for content to be eligible for display as a rich result.","Resolve validation errors to ensure pages are eligible for special search result features in Google. Review the 'Structured Data Details' tab for more information on specific errors and refer to Google rich result feature docs where necessary. Export unique validation errors using 'Reports > Structured Data > Validation Errors & Warnings Summary' and test in Google's Rich Results tool.",""
"Security: Missing Content-Security-Policy Header","Warning","Low","10201","52.270","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.",""
"Page Titles: Duplicate","Opportunity","Medium","52","0.520","Pages which have duplicate page titles. It's really important to have distinct and unique page titles for every page. If every page has the same page title, then it can make it more challenging for users and the search engines to understand one page from another.","Update duplicate page titles as necessary, so each page contains a unique and descriptive title for users and search engines. If these are duplicate pages, then fix the duplicated pages by linking to a single version, and redirect or use canonicals where appropriate.",""
"Links: Pages With High External Outlinks","Warning","Low","10079","100.000","Pages that have a high number of followed external outlinks on them based upon the 'High External Outlinks' preferences under 'Config > Spider > Preferences'. External outlinks are hyperlinks to another subdomain or domain (depending on your configuration). This might be completely valid, such as linking to another part of the same root domain, or linking to other useful websites. External followed outlinks can be seen in the 'Outlinks' tab, with the 'All Link Types' filter set to 'Hyperlinks' where the 'Follow' column is 'True'.","Review followed external outlinks to ensure they are to credible, trusted and relevant websites that are useful to your users.",""
"URL: Parameters","Warning","Low","6","0.030","URLs that include parameters such as '?' or '&'. This isn't an issue for Google or other search engines to crawl unless at significant scale, but it's recommended to limit the number of parameters in a URL which can be complicated for users, and can be a sign of low value-add URLs.","Where possible use a static URL structure without parameters for key indexable URLs. However, changing URLs is a big decision, and often it's not worth changing them for SEO purposes alone. If URLs are changed, then appropriate 301 redirects must be implemented.",""
"Meta Description: Over 985 Pixels","Opportunity","Low","2767","27.450","Pages which have meta descriptions over Google's estimated pixel length limit for snippets. Google snippet length is actually based upon pixels limits, rather than a character length. The SEO Spider tries to match the latest pixel truncation points in the SERPs, but it is an approximation and Google adjusts them frequently.","Write concise meta descriptions to ensure important words are not truncated in the search results, and not visible to users.",""
"JavaScript: Pages with Blocked Resources","Warning","High","10100","100.000","Pages with 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, or in bulk under 'Response Codes > Blocked Resource'.","Update the robots.txt and resolve any errors to allow all critical resources to be crawled and used for rendering of the websites content. Resources that are not critical (e.g. Google Maps embed) can be ignored.",""
"Structured Data: Parse Errors","Issue","High","12","0.120","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.",""
"H2: Non-Sequential","Warning","Low","1","0.010","Pages with an <h2> that is not the second heading level after the <h1> on the page. Heading elements should be in a logical sequentially-descending order. The purpose of heading elements is to convey the structure of the page and they should be in logical order from <h1> to <h6>, which helps navigating the page and users that rely on assistive technologies.","Ensure the <h2> is the second heading on the page. Headings should be in a logical sequential order from <h1> to <h6>. Review and update page heading levels so they are descending in order, for example the heading element following an <h1> should be an <h2>, rather than an <h3>.",""
"Page Titles: Over 60 Characters","Opportunity","Medium","1578","15.660","Pages which have page titles that exceed the configured limit. Characters over this limit might be truncated in Google's search results and carry less weight in scoring.","Write concise page titles to ensure important words are not truncated in the search results, not visible to users and potentially weighted less in scoring.",""
"Content: Low Content Pages","Opportunity","Medium","481","4.770","Pages with a word count that is below the default 200 words. The word count is based upon the content area settings used in the analysis which can be configured via 'Config > Content > Area'. There isn't a minimum word count for pages in reality, but the search engines do require descriptive text to understand the purpose of a page. This filter should only be used as a rough guide to help identify pages that might be improved by adding more descriptive content in the context of the website and page's purpose. Some websites, such as ecommerce, will naturally have lower word counts, which can be acceptable if a products details can be communicated efficiently.","Consider including additional descriptive content to help the user and search engines better understand the page.",""
"URL: Uppercase","Warning","Low","4","0.020","URLs that have uppercase characters within them. URLs are case sensitive, so as best practice generally URLs should be lowercase, to avoid any potential mix ups and duplicate URLs.","Ideally lowercase characters should be used for URLs only. However, changing URLs is a big decision, and often it's not worth changing them for SEO purposes alone. If URLs are changed, then appropriate 301 redirects must be implemented.",""
"Directives: Noindex","Warning","High","1579","15.480","URLs containing a 'noindex' directive in either a robots meta tag or X-Robots-Tag in the HTTP header. This instructs the search engines not to index the page. The page will still be crawled (to see the directive), but it will then be dropped from the index.","URLs with a 'noindex' should be reviewed carefully to ensure they are correct and shouldn't be indexed. If these pages should be indexed, then the 'noindex' directive should be removed.",""
"JavaScript: Contains JavaScript Content","Warning","Medium","9885","98.080","Pages that contain body text that's only discovered in the rendered HTML after JavaScript execution.","While Google is able to render pages and see client-side only content, consider including important content server side in the raw HTML.",""
"Meta Description: Below 400 Pixels","Opportunity","Low","170","1.690","Pages which have meta descriptions much shorter than Google's estimated pixel length limit. This isn't necessarily an issue, but it does indicate there might be room to communicate benefits, USPs or call to actions.","Consider updating the meta description to take advantage of the space left to include additional benefits, USPs or call to actions to improve click through rates (CTR).",""
"Security: Missing X-Content-Type-Options Header","Warning","Low","10201","52.270","URLs that are missing the 'X-Content-Type-Options' response header with a 'nosniff' value. In the absence of a MIME type, browsers may 'sniff' to guess the content type to interpret it correctly for users. However, this can be exploited by attackers who can try and load malicious code, such as JavaScript via an image they have compromised.","To minimise security issues, the X-Content-Type-Options response header should be supplied and set to 'nosniff'. This instructs browsers to rely only on the Content-Type header and block anything that does not match accurately. This also means the content-type set needs to be accurate.",""
"Meta Description: Below 70 Characters","Opportunity","Low","237","2.350","Pages which have meta descriptions below the configured limit. This isn't strictly an issue, but an opportunity. There is additional room to communicate benefits, USPs or call to actions.","Consider updating the meta description to take advantage of the space left to include additional benefits, USPs or call to actions to improve click through rates (CTR).",""
"Security: Protocol-Relative Resource Links","Warning","Low","10079","51.640","URLs that load resources such as images, JavaScript and CSS using protocol-relative links. A protocol-relative link is simply a link to a URL without specifying the scheme (for example, //screamingfrog.co.uk). It helps save developers time from having to specify the protocol and lets the browser determine it based upon the current connection to the resource. However, this technique is now an anti-pattern with HTTPS everywhere, and can expose some sites to 'man in the middle' compromises and performance issues","Update any resource links to be absolute links including the scheme (HTTPS) to avoid security and performance issues.",""
"Security: Missing X-Frame-Options Header","Warning","Low","10201","52.270","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.",""
"Response Codes: External Blocked Resource","Warning","Medium","104","0.380","External 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'.","If critical to your content, update the external subdomains robots.txt and resolve any errors to allow resources to be crawled and used for rendering of the websites content.",""
"Page Titles: Same as H1","Opportunity","Low","8284","82.190","Page titles which match the h1 on the page exactly. This is not necessarily an issue, but may point to a potential opportunity to target alternative keywords, synonyms, or related key phrases.","This is not necessarily an issue, but may point to a potential opportunity to target alternative keywords, synonyms, or related key phrases.",""
"URL: Underscores","Opportunity","Low","64","0.330","URLs with underscores, which are not always seen as word separators by search engines.","Ideally hyphens should be used as word separators, rather than underscores. However, changing URLs is a big decision, and often it's not worth changing them for SEO purposes alone. If URLs are changed, then appropriate 301 redirects must be implemented.",""