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:
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 = [
...,
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>',
'alexa': '<alexa verification code>',
}
The codes are alphanumeric and don’t include suffixes like ‘html’, e.g. 847e1f379a99c28a for google, not 847e1f379a99c28a.html.
Multiple codes are supported as well, except for bing:
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>',
),
'alexa': (
'<alexa verification code 1>',
'<alexa 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.
The Alexa codes I saw all had a length of 27 characters, so that’s what this app assumes is used. Please let me know if your codes differ and I need to modify the app.
Changelog
0.4.3 (2022-02-09)
Move tests to azure pipelines for now
0.4.2 (2020-08-24)
Repackage
0.4.1 (2020-08-24)
Fix issue with new verification yandex file
0.4.0 (2020-08-23)
Use docker-based travis testing
Test against Django >=3.0
Removed tests for Python 2, 3.4, and add 3.6 to 3.8
I only ran the tests, I don’t think I use it on any prod site right now
If any provider doesn’t work please let me know and I’ll probably remove it, I don’t have the time to work on this code. Or send patches.
Apologies for deleting issues, I deleted the old repo in between
0.3.0 (2016-02-20)
Python 2.7 and Django 1.8 are required
0.2.4 (2015-02-26)
Add Django 1.8 (beta1) support and drop 1.5 tests
0.2.3 (2014-04-13)
Django 1.7 (beta1) support
0.2.2 (2014-01-12)
Django 1.6 support
Removed Python 2.5 testing
0.2.1 (2013-03-25)
Add alexa support
Refactor the test project to use a different structure
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.4.3
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.4.3.tar.gz | 7.1 kB | Without provenance | Details for django-webmaster-verification-0.4.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_webmaster_verification-0.4.3-py3-none-any.whl | Python 3 | none | any | Details for django_webmaster_verification-0.4.3-py3-none-any.whl |
Total release size: 16.7 kB
Release files / django-webmaster-verification-0.4.3.tar.gz
| Download URL | django-webmaster-verification-0.4.3.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1cc6958ee4142da63c1b3e03e537cce6051c740cb1adf6afb68ddb1cc85f4e8f
|
|
BLAKE2b-256 checksum How to use checksums |
443df5ddb42ceeedda3098fa691920d77e44b33813834bc44fce40f0ce3fcdeb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.25.1 requests-toolbelt/0.9.1 urllib3/1.26.5 tqdm/4.62.3 importlib-metadata/4.10.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.2
|
Release files / django_webmaster_verification-0.4.3-py3-none-any.whl
| Download URL | django_webmaster_verification-0.4.3-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a79f906ab0986660eb27220fa6454ad487770b1ed13a9732a3e91054290c515d
|
|
BLAKE2b-256 checksum How to use checksums |
4937dcebacf1ffef205b564cd2255e597d4669a5446fb1d1766678b13e93844e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.25.1 requests-toolbelt/0.9.1 urllib3/1.26.5 tqdm/4.62.3 importlib-metadata/4.10.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.2
|
Security for django-webmaster-verification 0.4.3
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.