July 4, 2024
Let's get right into it.
Search Console has been down for a long time.
And everyone's complaining about it.
But, it's nothing new that Search Console's unreliable.
What's worse is that Search Console is lazy. Instead of indexing new blog posts right away, you have to wait -- sometimes for months -- before new pages are indexed.
So, to mitigate this you have to:
For every single blog post that you make.
This is annoying, and that's why we now have automatic Google Indexing. Simply attach your Search Console's Google account to one of your Wraith-connected accounts.
Then, every time Wraith publishes a new article for you, we'll automatically ask Google to index your new post.
One less thing to do if you're a busy entrepreneur.
OpenAI's Dalle-3 has been unreliable and crashes a lot (causing article jobs to crash), so we've switched to replicate AI for now. The outputs seem to be better than Stability AI's, but worse than Dalle-3's.
Replicate's much more reliable, but these open source text-to-image models just aren't at a very high level for blog posts.
We will explore Azure servers in the future to see if we can have a more reliable Dalle-3 endpoint.
Prior, Wraith Scribe can only integrate with Wordpress. While this is pretty great because most blogs run on Wordpress, it is somewhat restrictive.
For example, this SaaS site (and most SaaS sites and non-blog sites) won't run on Wordpress.
To make Wraith accessible for any and all website, we've added a way for Wraith to send a webhook notification to your website whenever a writing job's complete. Connecting Wraith to your website is as simple as a quick DNS entry verification. All you'd need to do after that is to process that POST request and publish the article on your particular setup.
The downside is that you need to have some basic coding skills, or know how to ask Claude / Chat GPT it up for you.
All articles give users the ability to scan main points by including a "Key Takeaways" section. However, the Table of Contents would include a pointer to this to every single article. This is OK, but Key Takeaways is part of the introduction, so I don't think it is necessary to pollute the TOC with Key Takeaways in every single article.
Now, TOCs generated will ignore the "Key Takeaways" section and only point your readers to the main meat of the article.
I've also updated the Wordpress Plugin to be able to make images native to your WP website. Prior, images were hosted in our S3 buckets for portability, but the URL would be something like:
us-east.aws.console.com/s3/buckets/path/to/image.jpeg
Now, the plugin takes the extra step to download and have it be hosted natively on your site. So instead of a long URL for the bucket, it'll be something like
yourwebsite.com/path/to/image.jpeg
Keeping links internal may be cleaner for SEO. Additionally, your website owning the image seems best-practice since it would imply your website owns the AI image as your own property.
We hope to:
