Duane Storey

Thanks for the kind words. And yes, I’m proud of Elevate. I have struggled getting people to try it since most people have a set it and forget it attitude with SEO and most don’t want to mess with the plugin they are currently using. But if your videos draw any people towards it, I hope they will find Elevate useful and powerful.

Elevate works fine with Fast CGI – unfortunately one of the detection routines I use during the wizard can’t obtain any information when Fast CGI is being used – but it’s just the detection routine and not the plugin. So anyone using Fast CGI can use the plugin fine (I use it on all my sites).

Thanks for using Elevate – and appreciate you including it in your videos.

Cheers,
Duane

Ok, marking this one as resolved, but if you still feel like there is another issue, please just open a new ticket. Thanks.

On the “Search” settings page, you can enable “Allow editing the index status”, and it should show up on each post.

So the original error is fixed then, i.e. private pages are being excluded now?

You said some pages are marked no-index, and they are still in the sitemap? Are they marked that way in Elevate? If so that’s another issue I’ll address.

Thanks,
Duane

If the admin there is a top level Elevate SEO menu at the very top – you should be able to regenerate the sitemap there.

Let me know if you need help.

Can you update to version 1.2.1 and see if that improves anything?

If not, perhaps you can set me up with an account and I can debug locally.

Thanks,
Duane

Hmm, looking at the code actually I’m surprised that’s the case. Can you give me an example of a post on your site?

Thanks,
Duane

Hi,

Yes, that would be a bug. I’ll push out an update this weekend I hope with that fix. Thanks for letting me know.

Duane

Great! Glad you found the solution – thanks for posting it for others.

Cheers,
Duane

Are there any PHP errors being generated on the site?

When I try now I get:

Forbidden
You don’t have permission to access \@backend on this server.
Additionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle the request.

So not sure if it’s because WordPress is throwing an error for robots.txt or something with the varnish config isn’t allowing the request through. I’m happy to debug this, just not sure where to start as on a normal WordPress install robots.txt works fine on all my test installations.

Hi,

It’s not a manual file, it’s just generated on demand from within WordPress. In theory any file that doesn’t exist will end up being processed from within WordPress.

You can see on my site – https://lindellwebstudios.com/robots.txt

That file doesn’t exist, Elevate is just outputting it via a hook. So it’s strange that’s not working for you. Can you tell me a bit more about your hosting environment? Where is it hosted? Is it Apache or Nginx?

Thanks,
Duane

Hi,

Can you possibly share your website URL with me? What plugins do you have installed?

Cheers,
Duane

Hi Glenn,

This should be resolved in 1.1.6.

Cheers,
Duane

You can send me an email at my first name and last name together (no space) at gmail. Thanks.

Hmm,

I’d probably have to debug this locally. Any chance you’d be willing to set me up with a temporary account to see what’s going on in the back end?

Outside of that can you possibly send me a list of all the plugins you have installed? Probably is a conflict with one of them.

Cheers,
Duane