"Issue Name","Issue Type","Issue Priority","URLs","% of Total","Description","How To Fix","Help URL" "Response Codes: Internal Client Error (4xx)","Issue","High","452","0.420","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.","" "URL: Non ASCII Characters","Warning","Low","8","0.010","URLs with characters outside of the ASCII character-set. Standards outline that URLs can only be sent using the ASCII character-set and some users may have difficulty with subtleties of characters outside this range.","URLs should be converted into a valid ASCII format, by encoding links to the URL with safe characters (made up of % followed by two hexadecimal digits). Today browsers and the search engines are largely able to transform URLs accurately.","" "Page Titles: Below 30 Characters","Opportunity","Medium","491","1.600","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.","" "Response Codes: External No Response","Warning","Low","806","0.740","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.","" "Security: Missing Secure Referrer-Policy Header","Warning","Low","81110","87.620","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.","" "Canonicals: Canonicalised","Warning","High","9079","29.530","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.","" "Structured Data: Rich Result Validation Errors","Issue","High","456","1.480","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.","" "Page Titles: Missing","Issue","High","2","0.010","Pages which have a missing page title element, the content is empty, or has a whitespace. Page titles are read and used by both users and the search engines to understand what a page is about. They are important for SEO as page titles are used in rankings, and vital for user experience, as they are displayed in browsers, search engine results and on social networks.","It's essential to write concise, descriptive and unique page titles on every indexable URL to help users, and enable search engines to score and rank the page for relevant search queries.","" "Structured Data: Parse Errors","Issue","High","348","1.130","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.","" "Security: Protocol-Relative Resource Links","Warning","Low","30745","33.210","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.","" "Structured Data: Rich Result Validation Warnings","Opportunity","Low","14777","48.060","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'.","" "URL: GA Tracking Parameters","Warning","Low","15","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.","" "JavaScript: Noindex Only in Original HTML","Issue","Medium","1","0.000","Pages that contain a noindex in the raw HTML, and not in the rendered HTML. When Googlebot encounters a noindex tag, it skips rendering and JavaScript execution. Because Googlebot skips JavaScript execution, using JavaScript to remove the 'noindex' in the rendered HTML won't work.","Carefully review pages with noindex in the raw HTML are expected to not be indexed. Remove the 'noindex' if the pages should be indexed.","" "H2: Duplicate","Opportunity","Low","13022","42.350","Pages which have duplicate