Pelican Redirect: A Plugin for Pelican
Redirect pages using meta http-equiv tags
Installation
This plugin can be installed via:
python -m pip install pelican-redirect
After the plugin is installed via pip, add pelican_redirect to your PLUGINS list in pelicanconf.py
PLUGINS = ['pelican_redirect', ...]
Usage
Once this plugin is installed, you can add a key to the frontmatter of the file called original_url. The plugin will generate an HTML page at that location that redirects to the new location of the post/page. Example:
Title: A sample title
original_url: blog-posts/2021/07/21/a-sample-title.html
Content here
Assuming this file is now going to be served from blog-posts/a-simple-title.html, a file will be written to blog-posts/2021/07/21/a-sample-title.html that redirects to the new URL.
If original_url does not have a file extension, or the file extension is something other than .htm or .html, then original_url is assumed to be a directory and index.html is appended to the URL.
Bulk Usage
To perform a page-wide redirect, you can use the CONTENT_REDIRECT_CONFIGURATION setting, which allows you to configure an original URL using page metadata. The structure of this configuration key looks like so:
CONTENT_REDIRECT_CONFIGURATION = [
{
"ARTICLE_URL": "old/layout/{slug}.html",
"PAGE_URL": "old/pages/{slug}.html",
}
]
For any entry in that list, if there is no key for the content type (for example, one configuration may only have ARTICLE_URL, another might only have PAGE_URL), the redirect will only be generated for the keys that are specified and the others will be skipped.
Contributing
Contributions are welcome and much appreciated. Every little bit helps. You can contribute by improving the documentation, adding missing features, and fixing bugs. You can also help out by reviewing and commenting on existing issues.
To start contributing to this plugin, review the Contributing to Pelican documentation, beginning with the Contributing Code section.
License
This project is licensed under the BSD-3-Clause license.
Metadata
Release files for pelican-redirect 3.0.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 | |
|---|---|---|---|---|
| pelican_redirect-3.0.0.tar.gz | 47.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pelican_redirect-3.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 52.7 kB
Release files / pelican_redirect-3.0.0.tar.gz
| Download URL | pelican_redirect-3.0.0.tar.gz |
|---|---|
| Size | 47.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44fdb03922c487be2fa776b0fb608c003ba012464e4a3dcd46baaeecd74a80d0
|
|
BLAKE2b-256 checksum How to use checksums |
dd0b5e1847898f934728b010dc1a991102af3f8882b89d8993934146d903d0ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2025.
Transparency logRelease files / pelican_redirect-3.0.0-py3-none-any.whl
| Download URL | pelican_redirect-3.0.0-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f70b99cbf315c24f77d642cfa8ae9bb47e4dbc822e660e3d170de2ca1a1f3ebf
|
|
BLAKE2b-256 checksum How to use checksums |
21660914c2d8590f51841e576c5ca82e7ee4a4e0ddc5d5e6b4e0d36bf8575343
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2025.
Transparency logSecurity for pelican-redirect 3.0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pelican_redirect-3.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2025.
Transparency logA 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.