Matt

So… may I ask why? How do you know there is a bug? What does it sound like doesn’t work properly to you?

BTW there are no error messages except notices which I have corrected, and disabling plugins has no effect on HTTP headers being sent.

Thanks Steve. I don’t think there’s any bad code – I’m assuming everything is working as it is supposed to. I’m just asking if there’s any way to disable WP sending headers when it doesn’t need to.

I see, no I believe I have always gotten these messages. Thanks!

Hi Steve, thanks for your response.
There most certainly are characters before the opening <?php, as this widget is loaded in the footer of my website template, so it’s not a hacking issue. I suppose I could create the wordpress instance in the header of my website prior to any output, but I feel as if there should be a better solution for anyone who wants to query WordPress further down the page.

Can’t think of anything off of the top of my head. They’re both different themes, the installation that works doesn’t have a changed database prefix, a few different plugins, but I disabled all plugins and switched the theme and it didn’t change anything. =/

Not working unfortunately. This is what it looks like.
https://imgur.com/9pAXeFE

Oddly enough I use this on other WP installations and it works on the others. It seems like this site is the only one it doesn’t work on.

It’s static

Each IP address is on its own line.
“166.176.XX.XXX
209.37.XXX.XX”

These are the log file contents.
“[10/19/2015 3:43 PM] – NOTICE : The following IP address range has been locked out for exceeding the maximum login attempts: 185.22.173
[10/19/2015 3:44 PM] – NOTICE : Login attempt from blocked IP range – 185.22.173.*
[10/19/2015 3:44 PM] – NOTICE : Login attempt from blocked IP range – 185.22.173.*
[10/19/2015 3:44 PM] – NOTICE : Login attempt from blocked IP range – 185.22.173.*
[10/19/2015 3:44 PM] – NOTICE : Login attempt from blocked IP range – 185.22.173.*
[10/19/2015 3:45 PM] – NOTICE : Login attempt from blocked IP range – 185.22.173.*
[10/19/2015 3:45 PM] – NOTICE : Login attempt from blocked IP range – 185.22.173.*”

I do not recognize this ip address.
Thanks for your quick response!

Hi jotademanuel,

It looks like all of your paginated pages are re-directing to your homepage for some reason. I can’t replicate the problem on your website.

As for my website it looks like this is fixed and all subpages of archives are being noindexed properly. Thanks guys.

Hi, I recently saw this bug on my pages too: https://www.bestattorney.com/blog/category/car-accidents/page/3

ah ok my apologies I didn’t see the ad the first time so I thought you were talking about the subheader.

I’d fix this by enclosing the h1 and h2 in a div, and floating the ad right. Should work pretty well. Let me know how it goes.

I’m assuming the correct link to your website is “https://www.iterationanddiscord.com” – what you have right now is not working.

I’m not sure what you want to do but if you’re trying to get the h1 and the h2 on the same horizontal line, I would float the h1 left and the h2 right, and set the h2 to clear:none;

sorry if that’s not what you wanted. Let me know if I can help with anything else.

the car-sickness one is showing for me in SF.
The Shelly page – as far as i can tell – has no links to it from your site, which would be why it isn’t showing in Screaming frog.
I’m not sure which of the 4 hospitals she works for but she wasn’t on any of the lists of vets, and your links to the hospital staff all return 404s (btw, i’d recommend creating a specific 404 page too! – right now all 404 pages are blank.)

btw, i think your redirection.js file just needs to be referenced with the full URL. to clean up those errors.
Were you not able to submit that car sickness page to the index in GWT?

Hi Alex,

Screaming frog crawls are working for me and are finding your blog posts. What does webmaster tools look like for you? Can you submit a fetch and render request on one of the blog posts?

I’m not sure what’s causing this but maybe spend some time cleaning up the 404 errors on your page and Google will have more of a crawl budget to spend time on your site?

marked as resolved