Issues

Meta Description: Multiple

back to issues overview

JavaScript
Noindex Only in Original HTML
Nofollow Only in Original HTML
Canonical Mismatch
Uses Old AJAX Crawling Scheme URLs
Uses Old AJAX Crawling Scheme Meta Fragment Tag
Pages with Blocked Resources
Contains JavaScript Links
Contains JavaScript Content
Page Title Only in Rendered HTML
Page Title Updated by JavaScript
Meta Description Only in Rendered HTML
Meta Description Updated by JavaScript
H1 Only in Rendered HTML
H1 Updated by JavaScript
Canonical Only in Rendered HTML
Pages With JavaScript Errors

PageSpeed
Eliminate Render-Blocking Resources
Properly Size Images
Defer Offscreen Images
Minify CSS
Minify JavaScript
Reduce Unused CSS
Reduce Unused JavaScript
Efficiently Encode Images
Serve Images in Next-Gen Formats
Enable Text Compression
Preconnect to Required Origin
Reduce Server Response Times (TTFB)
Preload Key Requests
Reduce JavaScript Execution Time
Serve Static Assets With An Efficient Cache Policy
Minimize Main-Thread Work
Image Elements Do Not Have Explicit Width & Height
Avoid Large Layout Shifts
Avoid Serving Legacy JavaScript to Modern Browsers
Avoid Multiple Page Redirects
Use Video Format for Animated Images
Avoid Excessive DOM Size
Ensure Text Remains Visible During Webfont Load

Accessibility
Best Practice – Accesskey Attribute Value Must Be Unique
Best Practice – Elements Must Not Have Tabindex Greater Than Zero
Best Practice – ARIA Dialog & Alertdialog Require Accessible Name
Best Practice – ARIA Treeitem Nodes Require Accessible Name
Best Practice – Role=text Should Have No Focusable Descendants
Best Practice – Form Elements Should Have Visible Label
Best Practice – Frames Should Be Tested With axe-core
Best Practice – Scope Attribute Should Be Used Correctly On Tables
WCAG 2.0 A – Scrollable Region Requires Keyboard Access
WCAG 2.0 A – Required ARIA Attributes Must Be Provided
WCAG 2.0 A – ARIA Attribute Must Be Used As Specified For Role
WCAG 2.0 A – ARIA Attributes Require Valid Values
WCAG 2.0 A – ARIA Attributes Require Valid Names
WCAG 2.0 A – ARIA Commands Require Accessible Name
WCAG 2.0 A – ARIA Input Fields Require Accessible Name
WCAG 2.0 A – ARIA Meter Nodes Require Accessible Name
WCAG 2.0 A – ARIA Progressbar Nodes Require Accessible Name
WCAG 2.0 A – ARIA Roles Must Be Contained By Required Parent
WCAG 2.0 A – ARIA Roles Require Valid Values
WCAG 2.0 A – ARIA Toggle Fields Require Accessible Name
WCAG 2.0 A – ARIA Tooltip Nodes Require Accessible Name
WCAG 2.0 A – Certain ARIA Roles Must Contain Specific Children
WCAG 2.0 A – Aria-braille Require Non-braille Equivalent
WCAG 2.0 A – Aria-hidden Elements Contains Focusable Elements
WCAG 2.0 A – Aria-hidden=true Must Not Be Used In <body>
WCAG 2.0 A – Elements Must Only Use Permitted ARIA Attributes
WCAG 2.0 A – Elements Must Use Allowed ARIA Attributes
WCAG 2.0 A – IDs Used In ARIA & Labels Must Be Unique
WCAG 2.0 A – Page Requires Means To Bypass Repeated Blocks
WCAG 2.0 A – Form <input> Elements Require Labels
WCAG 2.0 A – Frames Require Title Attribute
WCAG 2.0 A – Frames Require Unique Title Attribute
WCAG 2.0 A – Frames With Focusable Content Must Not Use tabindex=-1
WCAG 2.0 A – Page Must Contain <title>
WCAG 2.0 A – HTML Element Lang Attribute Value Must Be Valid
WCAG 2.0 A – HTML Element Requires Lang Attribute
WCAG 2.0 A – Image Button Requires Alternate Text
WCAG 2.0 A – Images Require Alternate Text
WCAG 2.0 A – <object> Elements Require Alternate Text
WCAG 2.0 A – Active <area> Elements Require Alternate Text
WCAG 2.0 A – Elements Marked role=img Require Alternate Text
WCAG 2.0 A – SVG Images & Graphics Require Accessible Text
WCAG 2.0 A – <video> Elements Require <track> For Captions
WCAG 2.0 A – <video> or <audio> Elements Must Not Auto-play
WCAG 2.0 A – Buttons Require Discernible Text
WCAG 2.0 A – Input Buttons Require Discernible Text
WCAG 2.0 A – Links Require Discernible Text
WCAG 2.0 A – Links Must Be Distinguishable
WCAG 2.0 A – Select Element Requires Accessible Name
WCAG 2.0 A – Summary Elements Require Discernible Text
WCAG 2.0 A – Deprecated <marquee> Element Must Not Be Used
WCAG 2.0 A – Interactive Controls Must Not Be Nested
WCAG 2.0 A – List Items Must Be Contained In List Elements
WCAG 2.0 A – Lists Must Only Contain <li> Content Elements
WCAG 2.0 A – <dt> & <dd> Elements Must Be Contained by <dl>
WCAG 2.0 A – <dl> Must Only Have Ordered <dt> & <dd> Groups
WCAG 2.0 A – <blink> Elements Deprecated & Must Not Be Used
WCAG 2.0 A – <th> Element Requires Associated Data Cells
WCAG 2.0 A – Table Header Attr Must Refer To Cell In Same Table
WCAG 2.0 AA – Meta Viewport Zoom & Scaling Disabled
WCAG 2.0 AA – Lang Attribute Requires Valid Value
WCAG 2.0 AA – Text Requires Higher Color Contrast to Background
WCAG 2.0 AAA – Text Requires Higher Color Contrast Ratio
WCAG 2.1 AA – Autocomplete Attribute Must Be Used Correctly
WCAG 2.1 AA – Inline Text Spacing Must Be Adjustable
WCAG 2.2 AA – Touch Targets Require Sufficient Size & Spacing
Best Practice – Skip-link Target Should Exist & Be Focusable
Best Practice – All Page Content Must Be Contained By Landmarks
Best Practice – Page Requires One Main Landmark
Best Practice – Page Must Not Have More Than One Banner Landmark
Best Practice – Banner Landmark Must Not Be In Another Landmark
Best Practice – Page Must Not Have Multiple Contentinfo Landmarks
Best Practice – Page Requires At Most One Main Landmark
Best Practice – Complementary Landmarks & Asides Must Be Top Level
Best Practice – Contentinfo Landmark Must Be Top Level Landmark
Best Practice – Main Landmark Must Not Be In Another Landmark
Best Practice – Landmarks Require Unique Role Or Accessible Name
Best Practice – Page Must Contain <h1>
Best Practice – Heading Levels Should Only Increase By One
WCAG 2.0 A – Form Field Must Not Have Multiple Label Elements
WCAG 2.0 A – HTML Lang & XML Lang Value Should Match
Best Practice – Ensure Elements Marked Presentational Are Ignored
Best Practice – ARIA Role Should Be Appropriate For Element
Best Practice – Headings Should Not Be Empty
Best Practice – Meta Viewport Should Allow Zoom & Scale Up to 500%
Best Practice – Alt Text Should Not Be Repeated As Text
Best Practice – Table Headers Require Discernible Text
Best Practice – Table With Identical Summary & Caption Text
WCAG 2.0 A – Deprecated ARIA Roles Must Not Be Used
WCAG 2.0 A – Server-Side Image Maps Must Not Be Used
WCAG 2.0 AAA – Delayed Meta Refresh Must Not Be Used
WCAG 2.0 AAA – Links With Same Accessible Name

Issues Meta Description Multiple

Pages which have multiple meta descriptions. There should only be a single meta description for each page.

Multiple meta descriptions are often caused by multiple conflicting plugins or modules in CMS.

How to Analyse in the SEO Spider

View URLs with this issue in the ‘Meta Description’ tab and ‘Multiple’ filter, and export all URLs using the ‘Export’ button.

What Triggers This Issue

This issue is triggered when a page has multiple meta descriptions. For example:

<meta name="description" content="About Us"> <meta name="description" content="About Screaming Frog.">

How To Fix

Remove additional meta description tags from the pages HTML, ensuring the website has a single, concise and relevant meta description for important pages.

Meta Description: Multiple

Multiple

How to Analyse in the SEO Spider

What Triggers This Issue

How To Fix

Further Reading

Back to top

Meta Description: Multiple

Multiple

How to Analyse in the SEO Spider

What Triggers This Issue

How To Fix

Further Reading

Back to top

SEO Spider v.21.1

SEO Spider v.21.1

SEO Spider v.21.1

Log File Analyser v.6.3

Log File Analyser v.6.3

Log File Analyser v.6.3

Support Ticket

Support Ticket

Training Request