Stories

I created 3 months' worth of SEO-friendly blog posts in 2 days using GPT-3

Article news.ycombinator.com

I created 3 months' worth of SEO-friendly blog posts in 2 days using GPT-3

I started a small productized SaaS business called growby.net. I am manually reaching out to potential companies to bring customers for growby and wanted to start SEO to boost some traffic. This is the process I follow. I am just sharing here to discuss the pros and cons of this approach.

Day 1:

1: Competitor Analysis: The first thing I did was to identify a competitor which is already ranking for the keywords I want to rank. I identified one website that was getting monthly traffic of 50k using search. I wanted to rank better for most of the keywords they are ranking.

2: Ahrefs Crawling of competitor's website: I did a scan of the competitor's website using Ahref's tool. Ahref gave me a list of around 45 blog post URL that was ranking nicely for them. Ahref also gave me a list of a total of 12000 keywords for all URLs combined. I exported all the data from Ahref in an Excel File. I aimed to finish 12 articles from this list of 45 in the next 2 days.

The above activity was to be done once only. now we will work on activities that have to be repetitive.

3: Keyword Clustering - GPT3 Entry :-) : I applied a filter on the URL and started working on the first blog post. The first article was about "Performance Appraisal in HR" and the competitor was ranking for almost 2500 keywords for it. I asked ChatGPT to do a clustering for all these 2500 keywords and I found a list of 10-12 important keywords. These are the keywords I want to target for creating the blog post.

4: Preparing Outline of the blog post - SEO META in 1 CLICK tool:

I opened the competitor's blog with the "Performance Appraisal in HR" related article and exported all the h1, and h2 tags using the "SEO META in 1 CLICK" plugin. I now got the article outline and the keywords for this page.

5: Actual Blog-Post creation using GPT3:

I just prompted the outline, and keywords in GPT3 to make a decent introduction, blogpost, conclusion, and key takeaways. It's important to ensure that the prompts are much more detailed to not get a generic reply.

6: Publish the blog post:

I published the blog post on my WordPress blog website. My blog post with almost 1500 words was ready with full research in just one day. A lot of time was spent in researching and identifying tools and preparing proper prompts for GPT3. I knew that the second day was going to be simple.

Day 2:

7: Publish the remaining 11 blog posts:

I just repeated steps number 3 to 6 for the next article and I was ready with it in the next 30 mins. I kept on creating till all 12 blog posts are created. I published them and did all the necessary design and usability changes. Each blog post is above 1000 words.

8: Update Sitemap and Search Console submission:

I used a free online crawling SEO tool to generate a sitemap and updated it on the website and the Google Search console. I did internal backlinking of all these blog-post to make them look proper.

9: Google Crawl and Indexing: Google has now started crawling and indexing these pages. I now need to create a list of backlinks and work on the technical SEO part.

10: Conclusion:

Each of the 12 blog posts I created is above 1000 words and I would have taken at least a week to write each blog post because of the research part and drifting away to Twitter, IH, etc. The 12 blog post would have taken me at least 12 weeks for sure.

I am yet to see any traffic/impression increase because of this work and so I have not resumed work for the remaining articles. I will have to work a lot on the suggestions provided by Ahref to increase the domain authority. I feel that if I stay consistent with this process, there is a probability to generate good traffic via SEO.

Discussion 4 comments · 6 points · milanspeaks · 2022-12-20
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.