This is a set of SEO tools for Django. It allows you to associate metadata with:
absolute paths
model instances
model classes
views
Metadata can be edited in the admin in a centralised place, but also alongside any associated models.
This is however a framework, not an app. You therefore have complete control over the data you store. Here is an example of a definition:
from rollyourown import seo
class BasicMetadata(seo.Metadata):
title = seo.Tag(max_length=68, head=True)
keywords = seo.KeywordTag()
description = seo.MetaTag(max_length=155)
heading = seo.Tag(name="h1")
subheading = seo.Tag(name="h2")
extra = seo.Raw(head=True)
# Adding some fields for facebook (opengraph)
og_title = seo.MetaTag(name="og:title", populate_from="title", verbose_name="facebook title")
og_description = seo.MetaTag(name="og:description", populate_from="description", verbose_name='facebook description')
As you can see it is very flexible, but there is much more than this simple example.
The full documentation can be read online at http://django-seo.readthedocs.org/.
Metadata
Release files for DjangoSEO 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| DjangoSEO-1.0.tar.gz | 200.6 kB | Without provenance | Details |
Release files / DjangoSEO-1.0.tar.gz
| Download URL | DjangoSEO-1.0.tar.gz |
|---|---|
| Size | 200.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e6889f5e28550a90f69ac34e96b811f7afb7627bf221ededae0ac93b35c243e
|
|
BLAKE2b-256 checksum How to use checksums |
a04453bf0fa00fab3ba594d8755556fad5b2106e22e70442005bcd0f6edabf88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for DjangoSEO 1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.