yoast/yoast-seo-for-typo3

Yoast SEO plugin for TYPO3

TYPO3 extension yoast_seo

Optimize your website for search engines with Yoast SEO for TYPO3. This extension integrates the text analysis and rating of Yoast SEO into the TYPO3 CMS interface. The content analysis can generate interesting metrics about a text and give you a score that can be used to improve the text and help editors write high quality content.

	URL
Repository:	https://github.com/Yoast/Yoast-SEO-for-TYPO3
Read online:	https://docs.typo3.org/p/yoast-seo-for-typo3/yoast_seo/main/en-us/
TER:	https://extensions.typo3.org/extension/yoast_seo

yoast-seo-for-typo3's Issues

Analysis doesn't update automatically when I edit the focus keyword

I have to first save the Yoast settings before the analysis updates.

Inheritance of settings, for example facebook image

There should be a setting to allow inheritance for subpages, for certain fields. It does not make sense for every field, but for some. If someone wants one global facebook image for example, this should be set on the root page, but should work for all subpages, if not overwritten. There are propably a few fields where this could make sense.

Deprecation warning in 1.0 with TYPO3 8 LTS

Hi there,

our installation of yoast creates the following entries in the deprecation log of a new TYPO3 8 instance:

21-06-17 07:08: Automatic TCA migration done during bootstrap. Please adapt TCA accordingly, these migrations will be removed. The backend module "Configuration -> TCA" shows the modified values. Please adapt these areas:
Using the 'type' = 'select' field in "pages['columns']['tx_yoastseo_robot_instructions']['config']['type'] = 'select'" without the "renderType" setting in "pages['columns']['tx_yoastseo_robot_instructions']['config']['renderType']" is deprecated.
Using the 'type' = 'select' field in "pages_language_overlay['columns']['tx_yoastseo_robot_instructions']['config']['type'] = 'select'" without the "renderType" setting in "pages_language_overlay['columns']['tx_yoastseo_robot_instructions']['config']['renderType']" is deprecated.

Changing title in snippet editor should change page path indication

Currently, when changing the title in the snippet editor the page path indication still shows the old title. It should display the updated title.

ieuws is the title here:

Robots meta tag on every page

Add a field to the page properties to let the user select specific directives for bots. For starters available options should be noindex, follow, index, nofollow, noindex, nofollow and possibly index, follow as a default selection.

https://yoast.com/robots-meta-tags/

Add support for setting a different focus keyword per language.

Because the focus keyword is just inserted without taking into account the different language variations of a page, the same focus keyword is used for all variations. The user should be able to set a focus keyword per language variation.

Add support for image blocks

Image blocks are not analyzed by the content analysis. They should be analyzed so we should convert those to image tags so YoastSEO.js can recognize these blocks as images.

Create tests for Travis

The plugin should be tested on Travis to keep the extension working with each code-change.

No indication of where a user can set a focus keyword

When a focus keyword is not provided, the SEO analysis shows the message "No focus keyword was set for this page. If you do not set a focus keyword, no score can be calculated".

However, there's no indication of where the user can set a focus keyword. It'd be nice to include a link to the "Edit page properties > Metadata" section within the message

The same applies to other metadata which may go unnoticed because they're kind of hidden under "Edit page properties > Metadata"

When I focus the snippet editor fields, the analysis collapses

This gives a weird UX. I would rather keep the analysis open and update semi-realtime after a some inactivity in typing. This needs to have a more intuitive feel.

Changing title in the snippet editor should update page tree

Currently, when changing the title in the snippet editor the title in the page tree still shows the old title. Changing the title in the snippet editor should update the page tree.

Add support for translations of YoastSEO.js

Make Readability and Focus keyword clickable

• Clicking Readability should take the user to the Readability analysis.

• Clicking Focus Keyword should take the user to the focus keyword field.

Broken Javascript in german translation file

In TYPO3 8.7.2, with v1.0, if I switch the language to German in the backend, I get a JavaScript error message "Uncaught SyntaxError: Invalid or unexpected token", which is caused by multiple special chars (u2028) in the translation file.

For example, see the first two occurences are after "plug-in!, here:

Error in links assessment

The SEO analysis shows the error below when the text contains a link.

• An error occurred in the 'textCompetingLinks' assessment
• An error occurred in the 'textLinks' assessment

Text example

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse convallis eros tortor, ornare tincidunt lectus feugiat eget. Praesent sagittis mauris et diam aliquam <a href="https://yoast.com/" title="my link">nec pulvinar purus</a>

Length bar always blue in Chrome

The bar colour for the tilte and the meta description should change (to orange or green) based on the number of characters entered. In Chrome, the bar is always blue-coloured.

Yoast SEO expects array

When installing the Yoast SEO extension in TYPO3 8.7.1 it throws an error.
It looks like it's expecting an array, but is not served an array.

See the attached screenshot for more information.

Snippet title field and normal title field should by synchronized

Currently, when changing the title in the snippet editor the title in the default title field isn't updated and vice versa. When updating one or the other they should stay synchronized.

Backend module icon

Add a correct icon to the backend module

Add support for hreflang

Because multilingual is a built-in part of TYPO3 it might be a good idea to include hreflang in the first version. I've discussed this with @arnoschoon and it looks like it isn't that much work to add a simple list of <link rel="alternate" href="..."> inside the head.

https://yoast.com/hreflang-ultimate-guide/

Autofill FB + Twitter

Twitter Bug

1. Twitter title - insert some text
2. Twitter description - is emtpy

Result of page: twitter title and description is filled with text of title.

Facebook OK

1. Facebook title - insert some text
2. Facebook description - is emtpy

Result of page: show only title.

Maybe it will be better empty description autofill with main decription of page.

TYPO3 CMS 8 LTS compatible

Make the extension work in TYPO3 CMS version 8 LTS

Remove dev-master from install instructions

Since you have a stable release now, please remove the dev-master part from the composer require command, so composer selects the stable version automatically.

TYPO3 exception when saving Facebook/Twitter image

Hello,
i tried to upload and save an image for Facebook and Twitter in the "Social" Tab in the Yoast SEO settings page. When i upload a new image to show on a Facebook/Twitter post i get after clicking on "Save" this TYPO3 exception:

Call to a member function addFile() on null

Error thrown in file
EXT:yoast_seo/Classes/Controller/ModuleController.php in line 285.

Uploading and saving the Facebook/Twitter image in the "Edit page properties" of my page works.

TYPO3 Version: 7.6.16
PHP Version: 7.0.15

SyntaxError: unterminated string literal

With TYPO3 backend language German the Yoast plugin shows only the spinner in the backend. In the browser console, the following error is shown:
SyntaxError: unterminated string literal

When you change the backend language to English, everything works as expected.

The problem probably occurs in wordpress-seo-de_DE.json.

Bullets show wrong colour

The checks below should show a green bullet

Scoping and flow must be improved for MVP

Currently, the elements aren't properly scoped and the flow doesn't work.

The snippet editor and analysis elements push down the content editor. Most metadata, including the focus keyword is now edited in the page property editor. Title and metadescription are also editable inline via the snippet editor. This isn't consistent.

Proposed solution.

We need one clearly scoped box with a title "Yoast SEO" above the content editor which contains the snippet preview, the focus keyword and expandable analysis sections. There should be an edit button. When I click that, I go to a dedicated edit page in which I get the full Yoast experience in which I can edit the SEO and social metadata and my focus keyword. It would be best to also show a snippet preview there and only the SEO analysis is needed in that context.

What do we want to achieve?

We want to integrate well with the Typo3 editorial experience. Inline editing isn't that common here. We can have "inline" editing on our dedicated editing page, but rather not on the page editor page. We do want to give users all the SEO context needed on that page, but when they want to edit metadata or content, they will have their dedicated pages for that as they are used to.

add basic auth support

Currently it's not possible to use the TYPO3 extension on basic auth protected sites. This will result in this error message in the TYPO3 backend:

Loading the page content preview failed
503 Service Temporarily Unavailable

SEO analysis doesn't work with gridelements

The analysis doesn't check content that is placed inside a gridelement.

Cannot set Facebook or Twitter image.

As a user I want to be able to upload a Facebook or Twitter image. This doesn't currently seem to be possible. This is a must have feature to be able to say we properly do Facebook and Twitter metadata.

Set the locale of YoastSEO.js to the locale of the current page variation

Current, we aren't passing a locale to YoastSEO.js. This means it defaults to English. It should, however, be set to the correct locale based on the current language variation.

Use proper RequireJS module to integrate with existing TYPO3 backend components

In order to be able to properly solve the following issues we need to use a RequireJS module which can interact with other TYPO3 interface components.

• #1
• #2
• #3

The core API of yoast-seo should be exposed using a RequireJS shim so it can be used transparently by the aforementioned module.

Mixed content warning in TYPO3 backend

Mixed Content: The page at 'https://www.foobar.tld/typo3/index.php?route=%2Fmain&token=9468b88b194666a86f8903a476ee4178f0eae9ef' was loaded over HTTPS, but requested an insecure image 'http://placehold.it/640cx480c?text=No%20image%20set'. This content should also be served over HTTPS.

The placeholder image is loaded vi http only.

Keyword density always shows 0%

No matter how many times the focus keyword appears in the text, the SEO analysis always says "The keyword density is 0%, which is too low; the focus keyword was found 0 times"

Add spinner when loading snippet preview

Add spinner when loading the snippet preview so when you're environment is slow, you have an indication the plugin is doing something.

Social SEO

Inserting og and twitter tags inside the head.

Add possibility to edit the slug within the snippet preview

It would be nice to have the possibility to edit the slug within the snippet preview. This option is available within the snippet preview but is now hidden due to issues building the right URL for TYPO3.

Use better slugify method inside the pretty URL module

Currently, we are simply lowercasing the title and replacing spaces with dashes, but the pretty URL module has a method to also replace special characters and make sure there are no repeated dashes. We should use this method to generate a slug for the page.

Improve readme and documentation

List some highlights of the plugin in README.md so the first glance of our repository gives users a good impression of some important features.

Give some insights and usage examples in ./Documentation/ so this also shows up at https://docs.typo3.org/.

Add support for multisites installations

If editor is logged in under one domain (domain1.com) he/she cannot use Yoast extension on other sites within same installation. Error message appears:
"Loading the page content preview failed
404 Not Found"
JS uses origin domain (domain1.com) as Request URL in $.get() function, instead correct one.

Add input field to change canonical

The user should be able to change the value that will be put inside the rel="canonical"

Error when accessing sysfolder in page module

When you are in the page module in the backend of TYPO3 and access a sysfolder, the preview can not be loaded and returns an error. It should be possible to set for which doktypes the preview is shown with a default of only pages.

Slug appended to SEO title in snippet editor

When the Slug field is not filled in, the snippet shows the SEO title in the permalink

When the Slug field is filled in, the provided slug should replace the SEO title in the permalink. Instead, the snippet editor appends the provided slug to the SEO title.

Red SEO score when number of characters is over the recommended minimum

When the number of characters in the text is over 300 the SEO score should be green, instead
it is red.

Note: This happens when no focus keyword is provided. If a focus keyword is provided, the bullet shows orange.

Create a CONTRIBUTING.md

You can use https://github.com/Yoast/wordpress-seo/blob/trunk/.github/CONTRIBUTING.md as inspiration.

Metadescription doesn't get printed on the frontend

Remove : after Focus keyword

Does not work with Flux / Fluidpages / Fluidcontent Extensions

This Extension is not working with FED Extensions (https://fluidtypo3.org/)

wrong message in the focus keyword alert

What did you expect to happen?

I modify the first paragraph to be compliant to the alert
"The focus keyword doesn't appear in the first paragraph of the copy. Make sure the topic is clear immediately."
I put the focus word in the first sentence and I expect the alert change

What happened instead?

in the tab Focus Keyword i still receive the messagge
"The focus keyword doesn't appear in the first paragraph of the copy. Make sure the topic is clear immediately."

How can we reproduce this behavior?

You can find the page I'm talking about in the demo instance
http://typo3-demo.maxserv.com
the page uid is 32

Slug is not saved

Slug field shows empty after filling in a slug and refreshing the page