How to get a blog to come up when a site is accessed

…businessbythebook.com.au…went to…businessbythebook.com.au/wp.

…tedsherwood.com…went to ‘Index.., ie. not the site.

If both are registered domains pointed to the same servers at one hosting account, you might first need to be certain they are each properly assigned and pointed at cPanel.

Could somebody flesh this answer out a little for me please? That is, tell me, in simple steps, how to check whether the assignment and pointing are as they are meant to be. (See my declaration at the end of my original post.)

Answers can vary from one host to another. Each of your domains lands at its own site, and each goes to where it was assigned at cPanel (if you have that) either prior to or during WordPress installation. If one is what your host would call a Primary Domain, you might not have had any choice about where (what folder) that domain is assigned and pointed to land unless it is redirected (like I do with .htaccess) after it arrives there. If your second domain is at that same hosting account, my host would call that an Add-On Domain and it could be assigned and pointed to any folder.

Do you have a problem you are trying to resolve?

Thanks for your help leejosepho.

I’m not too sure about domains and servers but here’s the deal:

I have two websites, both hosted by https://www.nerdster.com.au. I have the same deal for each website with Nerdster.

I installed WordPress via Softaculous on the first one and its URL was https://www.businessbythebook.com.au/wp. I put a blog as the front page of that website, and when somebody goes to https://www.businessbythebook.com.au they get my posts in that blog.

When I got the second website, tedsherwood.com I wanted the same thing to happen. But when I installed WordPress with Softaculous with the same settings – confirmed later via ‘Softaculous – Edit Page’ – the blog doesn’t come up when somebody goes to https://www.tedsherwood.com. What comes up is ‘Index…, i.e. nothing on the actual website. That’s my issue.

PS The second site works now, because Nerdster reinstalled WordPress in tedsherwood.com rather than tedsherwood.com/wp.

Nerdster is your host, and nerdster has servers that respond to browsers. You have two domains, and it sounds to me like each is assigned to its own sub-folder where I would guess .htaccess is invoking WordPress’ index.php to call wp-blog-header.php and so on. Nerdster re-installing WordPress to get your second domain working properly was possibly unnecessary since it sounds like possibly index.php was either not being called properly or could not be found since either the domain’s assignment to its folder might have been wrong or index.php had not actually been located there.

Sorry, but I don’t understand much of this, but if you tell where to go to check what you are saying, I could do that.

Nerdster has cPanel, I believe, and cPanel has File Manager where you should be able to look around a bit to see what folders (directories) you have and what is located where. You might see index.php in any of several places since that filename is used for various things, but each of your WordPress installations will have its own unique wp-config.php file. So when you locate wp-config.php, you have just found a WordPress installation in a folder than could be named just about anything. Then, I am guessing your WordPress installations will be in your hosting account’s folder I happen to know as public_html at BlueHost…and there is where my Primary Domain *must* be assigned and pointed by cPanel even though I can then use .htaccess to make it skip to any other folder where I might wish for it to actually land and do something.

OK.
businessbybook.com.au: wp-config.php is in /home/business public_html.
tedsherwood.com: wp-config.php is in /home/tedsherw public_html.
i.e. the same.
Or at least that’s one of them – remember I have two installations, one in tedsherwood.com and one in tedsherwood.com/wp.

Now what do I do?

businessbybook.com.au: wp-config.php is in /home/business public_html.
tedsherwood.com: wp-config.php is in /home/tedsherw public_html.

My host apparently does things a bit differently since I have something more like this:

/home/public_html/site1
/home/public_html/site2

But arrangement and nomenclature are not important here as long as browsers coming to your domains are arriving at the proper places.

Is there a problem you are trying to resolve?

I appreciate that you are trying to help, but we appear to be going round in circles. You’ve asked me again whether I have a problem. Yes, I do, and it is as I have stated twice above. See my original post.

Your original post is written in past tense, and each domain is currently landing at an installation. What is the problem?

I’m sorry that my English misled you. I will try again.

I have two websites.

When I install WordPress on each identically, that is, both with URLs of (website name)/wp they don’t behave the same way for the public. On the first one the website comes up when somebody types in its name, whereas on the second a backend page with ‘Index, wp….’ comes up.

What might be causing them to work differently?

Yes, I can cure the issue by installing WordPress in (website name) rather than (website name)/wp but I would prefer to have them both in a directory of their own.

on the second a backend page with ‘Index, wp….’ comes up.

That does not happen for me. https://businessbythebook.com.au/ comes up at one site, https://tedsherwood.com/ comes up at another (a new, empty site) and each is in its own folder at your server. Your sites’ folders do not show as parts of their paths because cPanel (and possibly some .htaccess) is sending your domains to the actual locations of their respective installations. If you are adding something to either of those URLs and getting undesirable results, that is likely because things are working just as they should. Actual server paths behind the curtain and what is used at the front are not the same thing.

See my fourth post above.