[FEATURE] Set Page Keyword Focus about cs_seo HOT 30 CLOSED

We will do this.

from cs_seo.

Excellent, it will be a really useful feature and help the extension become more of an analysis tool as well as administration.

Thank you.

from cs_seo.

I was wondering if you had any rough timeline for this feature? The reason I ask is we're about to carry out this work over about 700 pages for a large website update. I thought if it's coming soon it's worth waiting for, if not we'll just get started. It will still be really useful for everything we do in the future. Thanks

from cs_seo.

Today I will start with the work.

from cs_seo.

Great news, happy to test and feedback.

from cs_seo.

Hey,

so I created a new branch https://github.com/clickstorm/cs_seo/tree/evaluation . This is still under development. I check amongst other things when the focus keyword is set, if it appears in the browser title, the meta description and the content. Do you miss something?

You can test the dev Version. Clear all caches and make a DB update. There is a new Extbase-CommandController-Task in the scheduler to evaluate all pages. Because currenty I use curl to fetch the HTML it could take some minutes to evaluate all pages.

Tomorrow I will continue developing, e.g. to catch the pages_language_overlays etc.

Kind regards.

from cs_seo.

Hi, sounds great, we'll be testing it today.

I would say if possible, ignore grammatical words like and, in, or, a, of.... as google will ignore these and it would make your check fail if it's not an exact match. This could get quite complicated and is maybe just food for thought now.

When you say make a DB update, do you just mean update the current extension with this dev one? Or is this something else we have to do to try it?

Obviously we will back up, but is there any risk of losing our current metadata using by the extension while updating to the dev copy?

Thanks

from cs_seo.

I mean that after you pull the branch, you have to go to the database anylizer to update the database structure. Only a new table to save the scores will be inserted. So the current metadata will not be changed.

from cs_seo.

Hey @TheGrbTeam, did you test it already?

from cs_seo.

I wasn't totally sure on the safest way to add this new dev version so I'm waiting to hear back from our developer so he can do it. My concern was if I remove the current one to add this new one then it might delete the table with all our meta data in (over 500 pages worth). Would that be the case? We will be picking this up Monday now.

from cs_seo.

No, no fields will be deleted, only new fields will be added.

from cs_seo.

We're trying to add it but it seems to break it. At the moment we're renaming the old one to cs_seo_old and uploading the new one. Then we deactivate and reactivate cs_seo but it gives an error:

TYPO3 Fatal Error: Extension key "cs_seo_old" is NOT loaded!
It's a line in the ExtensionManagementUtility.php

This was how our developer thought it was done. The easiest way to update the db was to deactivate and reactivate... but obviously not. Sorry about this.

So it's safe to delete the current version we have of cs_seo, upload the new dev copy, then run the db analyser and we won't lose anything?

from cs_seo.

Yes this is safe. Of course you can reinstall the current version after you did the test. The database analyzer asks you what fields and tables you want to add. It also asks which fields and tables you would like to delete, if there are some. But he wont ask to delete sth. because only new field will be added.

from cs_seo.

You also can make a database dump if you want 100% to be sure.

from cs_seo.

Seems we have issues with accessing the install tool section where the analyser is, permissions problem I'm guessing. I'll update you when the devs have looked.

from cs_seo.

We are developing for thegrbteam who made this feature request.

We have added the version of cs_seo and the keyword focus field has appeared.

There is no counter though as described above in this thread where is tells us how many times and and where the keyword appears. Where is this counter supposed to appear?

from cs_seo.

Hi,

please update to the latest commit. The evalutaion is shown in the page module (maybe you have to update the extension manager configurations of the extension) and also in the SEO module. Bevore you see any results you have to press the Update button.

from cs_seo.

New main version 1.6.0 is available on TER. Maybe you can test this now.

from cs_seo.

Thank you mhirdes,

i will check it today.

from cs_seo.

Hi there,
I've tried the new keyword featured today, and it still doesn't seem to work. have tried across many pages too. Have attached screenshots of one example.

from cs_seo.

Did you update the database? The page must also be available in fronted. If the cache is off it could take some time until a page is analysed.

from cs_seo.

Yes we updated the DB and the page is available in the front end. Cache is on too. The keyword is set, we click update, it does the little animation and then still says no results.

from cs_seo.

I really would like to help you, but without an error message or anything I can't. Is the backend URL the same as the Frontend, also https:// and http://. Otherwise maybe you could send me a temporarily access.

from cs_seo.

Have you set a domain record in the root page?

from cs_seo.

Much appreciated. Could you provide your email and I'll get you temporary access.

On 1 Sep 2016, at 15:38, mhirdes <[email protected]mailto:[email protected]> wrote:

Have you set a domain record in the root page?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com//issues/10#issuecomment-244099581, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AT1ZrB_a0pLq40gVIQ86ufpxIMNtr1_Oks5qluNkgaJpZM4Jbn3T.

from cs_seo.

Sure: [email protected]

from cs_seo.

Hi, just checking you got access ok and if you have any news for us?

from cs_seo.

Hi, is there an issue? Did you get the login details?

from cs_seo.

I wrote you an answer.

from cs_seo.

The problem was an .htaccess protection. The server was not allowed to reach the frontend.
The solution is to give the server access for the frontend, so that the curl call could work. So add the line in your .htaccess file and replace the x with the IP from the server.

Allow from xxx.xxx.xxx.xxx

from cs_seo.