-
ignore tracking parameter
- equal to cHashExcludesParameters or more than those?
-
non yet translated pages => canonical to L=0
- what should be done for plugins that render L=0 content (because l=1 not yet availble) on L=1 pages (canonical should theoretically point to L=0)
-
API: Usecases:
- Plugins need to be able to define the canonical url of the current page, for e.g.
- search page 10 may be set to be canonical to page 1
- detail view in context of some category may be canonical to detail view without category
- who generates the url to the canonical url, the plugin or the canonical extension?
- plugin:
- PRO: EXT:canonical is not a wrapper for realurl
- CON: plugin will result faulty urls (e.g containing tracking parameters)
- EXT:canonical: vice versa the plugin notes
- plugin:
- Plugins need to be able to define the canonical url of the current page, for e.g.
-
user editable in page properties
- UX Problem. can be easily overlooked when content is changed and should no longer point to a different canonical. Probably a caution flag/message in the page overview would be needed
-
domain validation ==> no, trustedHostsPattern should suffice
-
domain limitation => One domain needs to be the canonical, maybe not the one the page is currently opened at
Last active
March 29, 2017 17:06
-
-
Save bnf/720217c09ce1d4938b803b7e9d587cdb to your computer and use it in GitHub Desktop.
Canonical TYPO3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment