Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Enable usage tracking filter

Open
#335 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
wordpress
Domain
documentation

Research direction

Start by investigating the wpseo_enable_tracking filter and the tracking settings described in the issue, including the linked WordPress plugin guidelines. Determine when the filter is useful without bypassing user consent, then document that use case and the recommended behavior in the developer portal.

Written by the indexing model from the issue text.

Description

Please give us a description of the issue

We have this filter add_filter( 'wpseo_enable_tracking', '__return_true' ); to enable tracking. What is the usecase of the filter? i.e. when we should use/recommend using the filter?

If the users' keep the tracking disabled from settings > site basics and from first time configuration, then our filter doesn't override the settings value and it is the correct output. In that case, when the filter can be useful?

  • I've read and understood the contribution guidelines.
  • I've searched for any related issues and avoided creating a duplicate issue.
Dominant language
JavaScript
Stars
15
Forks
23
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Yoast/developer

All issues in Yoast/developer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.