Title: <abbr title="Not Safe For Work / Mature content">[NSFW]</abbr> fetchpriority=&#8221;high&#8221; error
Last modified: October 12, 2023

---

# [NSFW] fetchpriority=”high” error

 *  Resolved [shaboneh](https://wordpress.org/support/users/shaboneh/)
 * (@shaboneh)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/fetchpriorityhigh-error/)
 * hi
 * This shows error for all pages of my site:
 * I chose different templates for the site, but this error is still taken by the
   plugin.
 * I know this is a tag html but I don’t know how to fix it.
 * Please help me
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffetchpriorityhigh-error%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Weston Ruter](https://wordpress.org/support/users/westonruter/)
 * (@westonruter)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/fetchpriorityhigh-error/#post-17120237)
 * This is a known issue. We were blocked on an upstream AMP spec update, which 
   I can see now has been done. You can follow [https://github.com/ampproject/amp-wp/issues/7601](https://github.com/ampproject/amp-wp/issues/7601)
   for updates.
 *  Thread Starter [shaboneh](https://wordpress.org/support/users/shaboneh/)
 * (@shaboneh)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/fetchpriorityhigh-error/#post-17120731)
 * Thanks for the tip.
   What should I do to fix this error?
 *  Plugin Author [Weston Ruter](https://wordpress.org/support/users/westonruter/)
 * (@westonruter)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/fetchpriorityhigh-error/#post-17122448)
 * You can just ignore it.
 * Otherwise, you can suppress it from being reported in the first place using the`
   amp_validation_error_sanitized` filter ([docs](https://amp-wp.org/reference/hook/amp_validation_error_sanitized/)).
   For example:
 *     ```wp-block-code
       add_filter(
       	'amp_validation_error_sanitized',
       	static function ( $sanitized, $error ) {
       		if (
       			'DISALLOWED_ATTR' === $error['code'] &&
       			'fetchpriority' === $error['node_name']
       		) {
       			$sanitized = true;
       		}
       		return $sanitized;
       	},
       	10,
       	2
       );
       ```
   
 * This can go in a custom plugin or your theme’s `functions.php`.
 *  Thread Starter [shaboneh](https://wordpress.org/support/users/shaboneh/)
 * (@shaboneh)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/fetchpriorityhigh-error/#post-17122714)
 * Thank you so much. If you suggest that we ignore this error, I prefer to listen
   to you
 * This error does not affect the index of our pages in Google?
 * Because we have installed “AMP” to increase the attention of Google
 *  Plugin Author [Weston Ruter](https://wordpress.org/support/users/westonruter/)
 * (@westonruter)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/fetchpriorityhigh-error/#post-17122884)
 * The AMP plugin identifies the error but it still sanitizes the markup to be valid
   AMP. So it doesn’t impact AMP validity. It’s more for your information to let
   you know it is removing something from your markup which you may have wanted.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘[NSFW] fetchpriority=”high” error’ is closed to new replies.

 * ![](https://ps.w.org/amp/assets/icon.svg?rev=2527602)
 * [AMP](https://wordpress.org/plugins/amp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/amp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/amp/)
 * [Active Topics](https://wordpress.org/support/plugin/amp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/amp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/amp/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Weston Ruter](https://wordpress.org/support/users/westonruter/)
 * Last activity: [2 years, 7 months ago](https://wordpress.org/support/topic/fetchpriorityhigh-error/#post-17122884)
 * Status: resolved