Changelog

🚀 Features

• New contentSelector property to define the selector for the main content of a page that should be analyzed for SEO.

🚀 Features

• Support Composer installation from a private repository.

🚀 Features

• As an alternative to both the keyphraseField and synonymsField properties (which are separate fields that an editor has to fill in) you can define keywords/keyphrases and synonyms directly in the blueprint:
  • keyphrase
  • synonyms

Both of these new properties support Kirby queries. For example, you can use the page title as a keyword next to a list of synonyms:

type: seo-audit
keyphrase: "{{ page.title.value }}"
synonyms:
  - Kirby
  - SEO
  - Audit

🐞 Bug Fixes

• Skip alt attribute assessment if the text doesn't contain any images.

🐞 Bug Fixes

• Convert Kirby translation format (POSIX locale format like es_ES) to IETF BCP 47 language tag format.

🚀 Features

• synonymsField option to add synonyms to the page's keyword or keyphrase.
• Custom SEO checks that complement the default assessments provided by Yoast SEO.
  • Alt attribute: Checks whether all images have an alt attribute.
  • Single H1: Checks whether the content contains a H1 heading.
  • Heading structure order: Checks whether the headings (H1 to H6) follow a proper sequential order.

🚀 Features

• Replace global transformers.proxyUrl option in the johannschopplich.seo-audit namespace with proxy, accepting two properties:
  • urlResolver for custom URL resolving.
  • params passed to Kirby's Remote::request() method.

🚀 Features

• Global transformers.proxyUrl option to further modify the request URL of the content fetcher proxy.

🐞 Bug Fixes

• Always return 200 status code from the proxy API path, but log the request error if it occurs.

🏎 Performance

• Externalize Yoast SEO translations into a separate build chunk to reduce the main bundle size.

🚀 Features

• Section property persisted to control if the report should be saved to local storage or not.

• Initial public release! 🌈🦄