etcbbu

Before I have done the wizard, I went to my individual “Edit Post” itself, scrolled down to where it seems to be the Yoast plugin stuff, clicked “Edit snippet”, and it then seemed to expand out a new field called “Meta description”, where I went ahead and put in what I wanted the description to be, and then clicked “Update” on the WordPress blog Post.

Now, when I open the live website, and look at the page source, it is giving me a line of code, saying

” <meta name="description" content="the words I want are here"/> ”

Should I take that to mean it is done? That my Blog Post now has its own Meta description that I wanted it to be?

• This reply was modified 8 years ago by etcbbu.

Thank you so much for the insights, @sterndata , you were most helpful!

–etcbbu

@wfalaa , it would appear I am good-to-go with enabling the Firewall on my WordFence plugin on my WordPress site! It says it was successfully enabled and everything.

Thank y’all for helping talk me through it.

–etcbbu

@wfalaa , Thank you so much for your insight.

I did not do anything described in that guide, because, no, I do not want to do what the beginning of that guide says:

Some people want their WordPress URL to coincide with their website's root (e.g. http://example.com) but they don't want all of the WordPress files cluttering up their root directory.

I really just want the entire blog site to be handled from

/mywebsite/subdirectory/

And that’s just fine.

So is it the .htaccess file in

/subdirectory/

that WordFence will make me back-up, and that I will replace with that backed-up version, in case the Firewall thing makes a change that throws off my site?

–etcbbu

• This reply was modified 8 years, 5 months ago by etcbbu.

Ok, so it will be in the same folder as where the three main WordPress folders are contained? Like, in the exact same folder alongside of

wp-admin
wp-content
wp-includes
index.php
license.txt
readme.html
etc. etc. …

?

Because on *my* WordPress site, it is not installed on my PRIMARY root folder of my entire website, but is installed in a sub-folder called

http://www.mywebsite.com/subfolder/

So, I would only be dealing with the .htaccess file that is in that

/subfolder/

correct? This is the place where

wp-admin
wp-content
wp-includes
index.php
license.txt
readme.html
etc. etc. …

are, for my site.

Ok, since I don’t trust that whatever hacked my site won’t be somehow left in the code if I were to do a backup and restore, I’m just gonna obliterate the MySQL database on my web-server, delete every single file in my entire

/blog/

sub-directory; start a new MySQL database, open a new sub-folder on my web-space, install a new WordPress Theme, re-edit the Theme to look a certain way, and re-publish all 27 Posts.

Can anyone recommend the best Virus/Protection/Firewall/Hacker-protection I could install that would be most helpful in the future, to help protect against being hacked?

I don’t see how it happened. I used the default Password that WP automatically generated for the main Admin account whenever I first installed this WP installation; those passwords are ridiculously long with many different types of characters, and I always kept my WP version up-to-date, and I had Akismet installed and kept *it* up-to-date, too.

Thanks for helping me think through this.

I don’t intend to back-up the MySQL database…I was going to obliterate it. Is that not possible? I definitely would have to backup the MySQL database too?