django-seo
Seo fields for objects of any model registed in admin or for specified url.
Installation:
Put seo as LAST item to your INSTALLED_APPS in your settings.py within your django project.
Sync your database:
./manage.py syncdb
Usage:
In settings.py:
Add names of ModelAdmins to be override:
SEO_FOR_MODELS = [
'<app>.models.<Model>',
]
In template:
First of all, load the seo_tags in every template you want to use it:
{% load seo_tags %}
- Use::
{% seo <title|keywords|description> [for <object>] %}
- Or::
{% seo <title|keywords|description> [for <object>] as <variable> %} {{ <variable> }}
Example:
settings.py:
INSTALLED_APPS = (
...
'app',
...
'seo',
)
SEO_FOR_MODELS = [
'app.models.Object',
'app.models.Another',
]
templates/object.html:
{% load seo_tags %}
<html>
<head>
<meta name="description" content="{% seo description for object %}" />
<meta name="keywords" content="{% seo keywords for object %}" />
<title>{% seo title for object %}</title>
</head>
<body>
{{ object.content }}
<h1>{% seo title for object as seo_title %}{{ seo_title }}</h1>
</body>
</html>
If you are using extend
templates/base.html:
<html>
<head>
<meta name="description" content="{% block description %}{% seo description %}{% endblock %}" />
<meta name="keywords" content="{% block keywords %}{% seo keywords %}{% endblock %}" />
<title>{% block title %}{% seo title %}{% endblock %}</title>
</head>
<body>
{% block content %}{% endblock %}
</body>
</html>
templates/object.html:
{% load seo_tags %}
{% block description %}{% seo description for object %}{% endblock %}
{% block keywords %}{% seo keywords for object %}{% endblock %}
{% block title %}{% seo title for object %}{% endblock %}
{% block content %}
{{ object.content }}
{% endblock %}
templates/another.html:
{% load seo_tags %}
{% block description %}{% seo description for another %}{% endblock %}
{% block keywords %}{% seo keywords for another %}{% endblock %}
{% block title %}{% seo title for another %}{% endblock %}
{% block content %}
{{ another.content }}
{% endblock %}
Redsolution CMS classifiers:
Metadata
Release files for django-seo 0.3.5
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 | |
|---|---|---|---|---|
| django-seo-0.3.5.tar.gz | 5.7 kB | Without provenance | Details |
Release files / django-seo-0.3.5.tar.gz
| Download URL | django-seo-0.3.5.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40b5614b35f19a01090442e187e678a8eb9a5e8e23101c4a32f1eca3b269e61a
|
|
BLAKE2b-256 checksum How to use checksums |
550acb2f9866d8560d33a7d2083dfce046a8da9f67e9ad19a41c28203175df72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-seo 0.3.5
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.