HGH Affiliate Ready Site for Sale OLD Domain Original Content


I want to sell HGH Affiliate Ready Site for Sale With OLD Domain Original Content.


Old Domain with Backlinks
Original Content Covering HGH and AntiAging and BodyBuilding
Beautifully Setup on WordPress
Top Selling Affiliate Setup

Assume No Traffic and Revenue as Site is Just Setup Few Days Ago.

Great Potential With Little Work.

BIN – $ 199

PM me for any questions or queries.


3 column layout for a song site. Sidebar on left/right, and content between them

So I’m working on a website, an anime one to be precise, where people can read about anime songs, their singers, rate them/post comments to them, add them to their list etc., and this is the current layout of the site of a song.

I think it’s decent, and I’m planning to keep it this way, but I’d like to know what others, maybe some experts think about this layout.

So as you can see, on desktop view there is a sidebar menu on the left(which can’t be closed), and there is another one on the right, which contains some info about the song, such as the embedded youtube video, some statistics, info about the singer(if exists),anime, and the lyrics at the bottom. Both sidebars and the div between them are separately scrollable, but the scrollbars are hidden, because IMO it would ruin the design/layout.

And between them the content div is placed, which contains further information about the song(statistics, song recommendations, comment section etc).

Their width goes like this: 20-65-15

Desktop view

Desktop view

On mobile view, the sidebar on the right is being pushed to the top of the content div, since it perfectly fits in the screen size of a phone, and of course the menu(but without the search section) can be opened with the usual hamburger menu icon, but unlike most sites, it’s placed on the bottom.

Mobile view

Mobile view

This layout is also convenient when the user wishes to read all the comments. On that site, the layout is still the same, so the sidebar on the right is still visible. But this time it’s only visible on desktop view, so this is one privilege of those who visit the site on a PC.

Site of all comments

Do you think a layout like this would be convinent for the users? Or isn’t it too unusual to have sidebars on both sides?

XSS and Content Security Policy, and existing CSS

I have done the first development of a website and deployment. Scanning the server with an online security evaluation tool I was recommended that I add a Content security Policy to the website, and I understand that this can help with XSS. But I read that this will disable inline CSS styles.

I have used inline CSS freely all over the website. Did not know this was a bad thing. (eg: div style=”width:100%;”). If I was to find and transfer all inline CSS to file it would take too long.

However I am only taking input from user in 3 pages. One is a feedback form that stores data on server only. One is a contact form that does not store data only send an email(collects user email address). The comments page takes comment input, stores the data, it retrieves and displays entries that have been cleared by admin. The other pages are mostly displaying static content.

I’m assuming comments page is the priority (is this right?). Would it work if I put CSP declarations (? default-src: https:) to the above three pages only (and remove inline CSS). and the others have inline enabled (? default-src: https: ‘unsafe-inline’) ?

Allow the user to toggle between 2 ways to display content on mobile?

So I have some page for a mobile app that I want to display a list of products. I have two options and I don’t know what to choose:

  1. Show items in a grid with a large picture and a small description (Assuming the phone is portrait, you can fit 2 items side by side, 2-3 rows, so there may be 4-6 items shown in the screen)
  2. Show items in a list, with a small picture and a medium-sized description (Kind of like a playlist in Apple Music)

Seeing as how both options can be good, as the casual users may prefer form over function (preferring option 1) and that the more detail oriented users may prefer function over form (preferring option 2), I feel like I should offer an option for users to toggle between the two. That seems to be the most natural solution, given that I find it hard to pick between the two.

However, that would mean I would have some sort of toggle button on the page, which may take away from the experience itself, ruining the aesthetics of the page, and making it more complicated.

So what should I do?

  1. Show a grid of items, thus focusing on aesthetics and potentially ruining the small minority of users who prefer more information
  2. Show a list of items, thus focusing on practicality, benefiting the small amount of people that do want the information, but potentially making the app more uglier for everyone else

  3. Add a button to toggle between the two views (on the same page), focusing on practicality for everyone, but ruining aesthetics for everyone (extra unneccessary UI elements and cognitive overload)

  4. Add a button to toggle between the two views, but in the settings. This doesn’t ruin the page with an unnecessary additional toggle button, and gives users who wish to see more details, the option to do so, hidden in the settings, and gives the ordinary casual user the aesthetics that they prefer. However I feel as though this may confuse users even more, especially if there are situations where a user may look at/use another user’s device and have some sort of unfamiliar UI. But maybe I’m just overthinking.

Can robots.txt be used to prevent bots from seeing lazily loaded content?

Let’s say that googlebot is scraping https://example.com/page.

  • example.com has a robots.txt file that disallows /endpoint-for-lazy-loaded-content, but allows /page
  • /page lazy loads content using /endpoint-for-lazy-loaded-content (via fetch)

Does googlebot see the lazy loaded content?