Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit

- [ v0.0.262 → v0.0.265](astral-sh/ruff-pre-commit@v0.0.262...v0.0.265)
- [ v3.3.2 → v3.4.0](asottile/pyupgrade@v3.3.2...v3.4.0)

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]>

Git stats


Failed to load latest commit information.
Latest commit message
Commit time
November 1, 2020 17:20
May 8, 2023 19:59
November 1, 2020 17:20
February 25, 2016 15:19
August 27, 2022 19:45
December 5, 2020 14:03
May 8, 2023 19:59
December 9, 2015 11:34


Join the Gitter chat Latest PyPI version Python versions Latest CI build status Test coverage Code Climate License

Meta tag information for django CMS 3 pages

Python: 3.7, 3.8, 3.9, 3.10

Django: 2.2, 3.2

django CMS: 3.7 - 3.10


  1. A working django CMS environment is required for djangocms-page-meta to work. Refer to django CMS documentation for how to install and configure django CMS.

  2. Install djangocms-page-meta:

    $ pip install djangocms-page-meta

    or from the repository:

    pip install -e git+
  3. Then add it to INSTALLED_APPS along with its dependencies:

  4. Migrate the database:

    $ python migrate
  5. Configuration:

    See usage and configuration section in the documentation.

  6. That's all!


Enabling this will hide django CMS own Meta description field to keep all the meta information in the same part of the interface. If the django CMS field is set, it will still be shown (and used by djangocms-page-meta).

django-app-enabler support

django-app-enabler is supported.

You can either

  • Installation & configuration: python -mapp_enabler install djangocms-page-meta
  • Autoconfiguration: python -mapp_enabler enable djangocms_page_meta

Fully using this package will require some template changes that cannot be modified by django-app-enabler:

  • Load template tag in the page like outlined in usage page;
  • Run migrations: python migrate

Check usage documentation for details.



For package documentation see