Exclusions settingsAccelerator for WordPress

Here can be specified pages’ URLs that should be excluded from processing by both caching as content processing engines.

Note. There are additional user exclusion argument settings that are used independently.

settings-Exclusions

URI paths#

Only matched pages’ URLs will be excluded.

Syntax#

Pages’ URLs beginning these strings in their paths will be matched. You can add parts with or without a / at the beginning.

Regular expressions are also supported. Current path is always compared without beginning slash. E.g. if you want to match all pages except site’s root then you need to add @^[^/].*@ expression. Any regular expression quote symbols except / can be used.

Note. These strings are always related to site’s root address. E.g. if site URL is https://mysites.com/one and you want to match https://mysites.com/one/subdir, then you need to add only subdir to the list.

URI arguments#

  • Exclude all

    If checked, all pages’ URLs having any arguments will be excluded.

  • Exclude list

    Pages’ URLs having arguments that begin with any of the specified strings will be excluded.

  • Cache skip all

    If checked, all pages’ URLs having any arguments will be treated as without arguments and cached as the same items. E.g. https://mysite.com/page1?a1=1&a2=2 will be processed as https://mysite.com/page1.

  • Cache skip list

    Pages’ URLs having arguments that begin with any of the specified strings will be treated as without these arguments and cached as the same items. E.g. if ‘a1’ is specified then https://mysite.com/page1?a1=1&a2=2 will be processed as https://mysite.com/page1?a2=2. It increases pages’ response speed when they are, for instance, opened from external sources appended by tracking arguments like Facebook’s fbclid.

Agents#

Pages’ requests having these strings in their user-agents will be excluded.

Cookies#

Pages’ requests having cookie names that begin with any of the specified strings will be excluded.

Content’s patterns#

Here you can specify parts of the pages via their XPaths. If any of elements is matched with specified patterns on the page it will be excluded from caching. Since XPath language it is an analogue of CSS, it allows you to make settings both for individual pages and for their set, using the principle of CSS selectors (classes, tags, properties, …).

E.g. this expression finds only empty element (without children) with class some-class:

.//*[contains(concat(" ",normalize-space(@class)," ")," some-class ")][count(./*)=0]

Note. These exclusions are checked while optimization process instead of other exclusions that checked immediately while accessing pages. So, all excluded pages can be seen in optimization queue.

Leave a Reply