Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-sites domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rank-math domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the insert-headers-and-footers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Deprecated: ActionScheduler_Store::save_action(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Store.php on line 29

Deprecated: ActionScheduler_Store::stake_claim(): Implicitly marking parameter $before_date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Store.php on line 188

Deprecated: ActionScheduler_Store::get_scheduled_date_string(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Store.php on line 257

Deprecated: ActionScheduler_Store::get_scheduled_date_string_local(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Store.php on line 274

Deprecated: ActionScheduler_DBStore::save_unique_action(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 55

Deprecated: ActionScheduler_DBStore::save_action(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 68

Deprecated: ActionScheduler_DBStore::save_action_to_db(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 82

Deprecated: ActionScheduler_DBStore::stake_claim(): Implicitly marking parameter $before_date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 795

Deprecated: ActionScheduler_DBStore::claim_actions(): Implicitly marking parameter $before_date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 860

Deprecated: ActionScheduler_Logger::log(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Logger.php on line 28

Deprecated: ActionScheduler_Logger::log_failed_fetch_action(): Implicitly marking parameter $exception as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Logger.php on line 142

Deprecated: ActionScheduler_DBLogger::log(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBLogger.php on line 21

Deprecated: ActionScheduler_QueueRunner::__construct(): Implicitly marking parameter $store as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php on line 39

Deprecated: ActionScheduler_QueueRunner::__construct(): Implicitly marking parameter $monitor as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php on line 39

Deprecated: ActionScheduler_QueueRunner::__construct(): Implicitly marking parameter $cleaner as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php on line 39

Deprecated: ActionScheduler_QueueRunner::__construct(): Implicitly marking parameter $async_request as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php on line 39

Deprecated: ActionScheduler_Abstract_QueueRunner::__construct(): Implicitly marking parameter $store as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php on line 34

Deprecated: ActionScheduler_Abstract_QueueRunner::__construct(): Implicitly marking parameter $monitor as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php on line 34

Deprecated: ActionScheduler_Abstract_QueueRunner::__construct(): Implicitly marking parameter $cleaner as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php on line 34

Deprecated: ActionScheduler_QueueCleaner::__construct(): Implicitly marking parameter $store as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueCleaner.php on line 35

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rank-math-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uael domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Deprecated: Creation of dynamic property RankMathPro\BBPress::$meta_key is deprecated in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math-pro/includes/modules/bbPress/class-bbpress.php on line 32

Deprecated: Creation of dynamic property RankMathPro\Analytics\Email_Reports::$views_path is deprecated in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math-pro/includes/modules/analytics/class-email-reports.php on line 49

Deprecated: Creation of dynamic property RankMathPro\Analytics\Email_Reports::$assets_url is deprecated in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/seo-by-rank-math-pro/includes/modules/analytics/class-email-reports.php on line 50

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Deprecated: Elementor\Controls_Stack::get_active_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/base/controls-stack.php on line 334

Deprecated: Elementor\Controls_Stack::get_active_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/base/controls-stack.php on line 334

Deprecated: Elementor\Controls_Stack::get_style_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/base/controls-stack.php on line 795

Deprecated: Elementor\Controls_Stack::get_style_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/base/controls-stack.php on line 795

Deprecated: Elementor\Elements_Manager::create_element_instance(): Implicitly marking parameter $element_type as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/managers/elements.php on line 71

Deprecated: Elementor\Element_Base::__construct(): Implicitly marking parameter $args as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/base/element-base.php on line 1498

Deprecated: Elementor\Repeater::__construct(): Implicitly marking parameter $args as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/elements/repeater.php on line 49

Deprecated: Elementor\Core\Utils\Collection::filter(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/core/utils/collection.php on line 43

Deprecated: ElementorPro\Modules\Forms\Submissions\Actions\Save_To_Database::save_action_log(): Implicitly marking parameter $exception as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor-pro/modules/forms/submissions/actions/save-to-database.php on line 143

Deprecated: {closure:ElementorPro\Modules\Forms\Submissions\Actions\Save_To_Database::__construct():177}(): Implicitly marking parameter $exception as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor-pro/modules/forms/submissions/actions/save-to-database.php on line 177

Deprecated: Function WP_Dependencies->add_data() was called with an argument that is deprecated since version 6.9.0! IE conditional comments are ignored by all supported browsers. in /home/quirkysi/quirkyold.quirkysite.com/wp-includes/functions.php on line 6170

Deprecated: Elementor\Core\Files\CSS\Post::add_controls_stack_style_rules(): Implicitly marking parameter $all_controls as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/core/files/css/post.php on line 221

Deprecated: Elementor\Core\Files\CSS\Base::add_controls_stack_style_rules(): Implicitly marking parameter $all_controls as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/core/files/css/base.php on line 549

Deprecated: Elementor\Core\Files\CSS\Base::get_active_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/core/files/css/base.php on line 907

Deprecated: Elementor\Core\Files\CSS\Base::get_active_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/core/files/css/base.php on line 907

Deprecated: Elementor\Core\Files\CSS\Base::get_style_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/core/files/css/base.php on line 935

Deprecated: Elementor\Core\Files\CSS\Base::get_style_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/core/files/css/base.php on line 935

Deprecated: Elementor\Core\DynamicTags\Dynamic_CSS::add_controls_stack_style_rules(): Implicitly marking parameter $all_controls as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/core/dynamic-tags/dynamic-css.php on line 104

Deprecated: Elementor\Stylesheet::add_rules(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/stylesheet.php on line 141

Deprecated: Elementor\Includes\Widgets\Traits\Button_Trait::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/widgets/traits/button-trait.php on line 459

Deprecated: Elementor\Includes\Widgets\Traits\Button_Trait::render_text(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/includes/widgets/traits/button-trait.php on line 567

Deprecated: ElementorPro\Modules\Posts\Traits\Button_Widget_Trait::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor-pro/modules/posts/traits/button-widget-trait.php on line 411

Deprecated: ElementorPro\Modules\Carousel\Widgets\Media_Carousel::print_slider(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor-pro/modules/carousel/widgets/media-carousel.php on line 269

Deprecated: ElementorPro\Modules\Carousel\Widgets\Base::print_slider(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor-pro/modules/carousel/widgets/base.php on line 544

Deprecated: ElementorPro\Modules\Payments\Widgets\Paypal_Button::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor-pro/modules/payments/widgets/paypal-button.php on line 220

Deprecated: ElementorPro\Modules\Payments\Classes\Payment_Button::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor-pro/modules/payments/classes/payment-button.php on line 504

Deprecated: ElementorPro\Modules\Payments\Widgets\Stripe_Button::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor-pro/modules/payments/widgets/stripe-button.php on line 244
Duplicate Meta Descriptions | Quirky Digital

Why Should I Avoid Duplicate Meta Descriptions?

A google search for analytics to demonstrate the search for why should I avoid duplicate meta descriptions

According to Google, quality meta descriptions are one of the key parts of optimising your search appearance..

The Yoast SEO plugin, being used to review multiple pages that has duplicate meta descriptions

Meta descriptions are the small block of text you see in the SERPs just below the URL. They allow you to write 1-2 small descriptive sentences informing the visitor as to the page they are about to visit.

If you have a large e-commerce website with hundreds of products and decide to automatically generate your own meta descriptions – this will cause a flurry of duplicate meta descriptions which is not ideal.

With this, you may be asking yourself “Why should I avoid duplicate meta descriptions?” That is what we will explain below.

 

What Are Duplicate Meta Descriptions?

Duplicate meta descriptions are meta descriptions that feature the same text across multiple pages on your website.

As mentioned above, this tends to happen as a time-saving tool to publish all of the required pages on your website.

By doing this, however, you are sacrificing the amazing opportunity that meta descriptions allow.

 

Why Should I Avoid Duplicate Meta Descriptions?

Meta descriptions provide you with the opportunity to sell your wide array of pages, products or services with 1-2 descriptive sentences. Not to mention, informing search engines of what each of your pages represents.

Meta descriptions also allow you to implement one or even two keywords that you wish your products/services to rank for.

You might think that having a large number of duplicate meta descriptions may penalise you and see your rankings drop? They will have an effect on your rankings, but not through being penalised.

Simply put, if your website has various pages with the same meta descriptions – you should not expect to have one key service or product to outrank another as they have the same meta description.

A screenshot of the Google Search Engine

 

How To Find Duplicate Meta Descriptions?

The tool that we suggest using is Screaming Frog. Screaming Frog is a fantastic website auditing tool that allows you to get a full grasp of a website’s condition.

Regarding finding duplicate meta descriptions, it is also really straightforward. Once you have run your website through Screaming Frog, find the ‘Meta Description’ tab on the top left hand side. after you have clicked it, you will see an overview of your meta descriptions appear.

Underneath ‘All’ and ‘Missing’ – you will find ‘Duplicate’. If you are showing as 0 duplicate meta descriptions, then there is nothing to worry about.

However, if you do have pages, Screaming Frog will identify them for you so you can go into the pages and address them.

 

Why Do Meta Descriptions Matter?

One of the main goals for SEO is to have a decent click-through rate. If you are unsure as to what is meant by click-through rate: Click-through rate essentially measures the total number of people who have clicked on a link against the total number of those who have seen the link and decided to not click on it.

Your page title will always be the first thing that organic traffic will see before they decide to enter one of your pages.

Meta descriptions will ultimately be the second and in some cases can be the deciding factor as to whether a visitor will click-through.

Regardless of what page you are writing your main goal is to make sure that the meta description has a clear understanding regarding what the page represents, as well as being quite informative.

With that being said, it is important to understand the difference between informative and unprofessional.

For example, if you are solicitors – you want to make sure that your meta descriptions don’t come across as informative as potential visitors will be likely to look elsewhere.

If you have an eCommerce website, however, it may be wise to get an understanding of your target demographic and tailor your copy to that demographic. That way you are writing in a style that speaks to your audience.

 

Things To Consider With Meta Descriptions?

When it comes to writing a meta description, often you may find that the first sentence needs the most work. Usually, the first sentence serves as an introduction to the page, giving visitors an insight into what they are about to visit.

The second sentence usually allows you to implement a keyword that invites the user to actually click through. If your description doesn’t completely represent what your page is about, this can often cause traffic to leave which will boost your bounce rate percentage and ultimately harm your overall rankings.

It is also important to know that Google may not always use the meta description that you have set. For instance, you might have the best meta description in the world for a particular product or service and find that Google has either taken a snippet of your text on the page or they might choose a subheading. They could even take the first few lines of the text.

To write a meta description, you usually have 155-160 characters to work with. So it is important that when you are addressing your duplicate meta description issue – you write a compelling description with your keyword(s) in there while also not exceeding the character limit.

Exceeding the limit will mean that the descriptions will start to truncate. Truncation will not penalise you, this is fairly common to see as truncation can happen at fairly different lengths, but it is important to keep an eye on it.

 

A Summary Of Should I Avoid Duplicate Meta Descriptions

Having duplicate meta descriptions might be incredibly harmful to your SEO. Although your pages won’t be penalised, you shouldn’t expect a particular page to rank better than another as they both have the same meta description.

As you are eliminating your duplicate meta descriptions by writing your own meta descriptions, you should make sure that they are written in a way that speaks to your audience whilst also injecting your main keyword(s) into the sentences.

Sign Up For Free SEO Mini Course

Our founder, Liam Quirk, has got to work on a culmination of in-depth articles, practical tutorials, and engaging videos – all taken from years of hands-on experience and prolonged success in the SEO game.


Deprecated: Constant E_STRICT is deprecated in /home/quirkysi/quirkyold.quirkysite.com/wp-content/plugins/elementor/core/logger/manager.php on line 250