What term should be used when defining a page in the admin menu that allows you to change a plugins options?

  • While the question regarding the difference in WordPress terminology between settings and options is valid, asking which term to use for a settings/options page label in the admin menu is primarily opinion-based. Commented Apr 18, 2014 at 20:16

2 Answers 2


These two are pretty close, but relate to slightly different stages of the process. In purely technical terms WordPress has two different APIs — Options API and Settings API.

Options API deals with saving and retrieving options from database. So its scope and scope of "options" in terminology is that of purely storage.

Settings API deals with admin pages, forms, receiving/validating/sanitizing data, and finally using Options API to store it. So in terminology it refers more or less to level of admin interface and user interaction.

Depending on nature of your plugin its page should be named either after its own name or after what plugin does. Then it should be nested appropriately in a level such as Settings or Appearance. Creating top level pages for the plugins is not uncommon, but is often considered overblown and annoying, especially so if the plugin/theme doesn't have many things to put there.

  • The terms options and settings are all too often used interchangeably (and therefore confusingly). This is an excellent explanation of the distinction between the two.
    – vancoder
    Commented Apr 18, 2014 at 21:12

You should just use the name of the plugin. No need to concatenate "options" or "settings" to it.

A lot of times (if the plugin is small, or you rarely need to change it's settings) you place the plugins admin page under the "Settings"-page that already exists.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.