README
======
This application allows various webmaster tools to verify that a django site is
managed by you.
The only supported method of verification is by accessing a file on your
server.
Supported services:
- `Google Webmaster Tools <https://www.google.com/webmasters/tools/home>`_
- `Bing Webmaster Tools <https://ssl.bing.com/webmaster/Home/>`_
- `Yandex Webmaster Tools <http://webmaster.yandex.com/>`_
- `Majestic SEO <https://www.majesticseo.com>`_
Usage
=====
Get ``django-webmaster-verification`` into your python path::
pip install django-webmaster-verification
Add ``webmaster_verification`` to your INSTALLED_APPS in settings.py::
INSTALLED_APPS = (
...,
'webmaster_verification',
...,
)
Add ``webmaster_verification`` to your root urlconf (urls.py)::
urlpatterns = patterns('',
...,
url(r'', include('webmaster_verification.urls')),
...,
)
Add settings just as::
WEBMASTER_VERIFICATION = {
'bing': '<bing verification code>',
'google': '<google verification code>',
'majestic': '<majestic verification code>',
'yandex': '<yandex verification code>',
}
The codes are alphanumeric and don't include suffixes like 'html', e.g.
``847e1f379a99c28a`` for google, not ``847e1f379a99c28a.html``.
Multiple codes for google, yandex and majestic are supported as well::
WEBMASTER_VERIFICATION = {
'bing': '<bing verification code>',
'google': (
'<google verification code 1>',
'<google verification code 2>',
),
'majestic': (
'<majestic verification code 1>',
'<majestic verification code 2>',
),
'yandex': (
'<yandex verification code 1>',
'<yandex verification code 2>',
),
}
Notes
-----
As **Bing** always accesses the same verification file I'm not sure if it's
possible to support more than one code for it. Please let me know if yes, and
how, as I don't really use their tools.
For **Yandex** only the `.txt` file method is supported, but adding support for
`.html` should be trivial.
Changelog
=========
0.2 (2013-02-16)
----------------
- Python 3.2 support
- Integrate testing with travis
0.1.10 (2012-12-21)
-------------------
- Fix test errors when running from a real project
0.1.9 (2012-12-19)
------------------
- Pypi updates
0.1.8 (2012-12-19)
------------------
- Yandex Webmaster Tools support added.
0.1.7 (2012-05-07)
------------------
- Bugfix for multiple verification codes for one provider.
Metadata
Release files for django-webmaster-verification 0.2
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 | Actions |
|---|---|---|---|---|
| django-webmaster-verification-0.2.tar.gz | 5.6 kB | Without provenance | Details for django-webmaster-verification-0.2.tar.gz |
Release files / django-webmaster-verification-0.2.tar.gz
| Download URL | django-webmaster-verification-0.2.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d23b228633b6ad1b2b61bce6ef8aa452d7480683bf3450794b24b9afc3047cb
|
|
BLAKE2b-256 checksum How to use checksums |
226a36844e7c765f6eea881425c7e963c355c4cddc632edf3fe181ed054ee329
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-webmaster-verification 0.2
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.