Hi developers and support managers.
I'm trying to make a blog using pure HTML/CSS and JavaScript.
Here I've implemented a design check readersmess.
I just needs a guide which backend should I use to store my blog posts. I already tried to use firestore but my post was not indexing to google.
I was reading id from url to fetch data from firestore.
Kindly suggest me the best method. I don't want to move from firebase hosting. How can I use other libraries to store and fetch posts so that post should be indexed in google?
To make your site discoverable, try to follow the basic steps that optimize your site for search engines (such as referrals on other sites, using descriptive titles, etc.) as described in the Google's basics guide.
After that, you can take an active approach in your URLs management and create and submit a list of your URLs (sitemap) to Google that can improve the discovery of your site:
By providing our systems a direct list of URLs to your content, known
as a sitemap, our ability to find your pages no longer relies solely
on your page's relationship to other referring pages on the wider web.
This speeds up the process of our systems discovering your content.
Typically, you host the sitemap on your domain in a place accessible
by Googlebot.
For the general overview and instructions on how to create and submit a sitemap, refer to the Sitemaps guidelines.
Related
I developed a website using Nextjs (Client side only, and used Nextjs for the SEO).
I wanted to ask if there is a way to convert this website somehow from Nextjs to Wordpress or anything else, or even somehow connect it to CMS application, so my client can modify images and content any time he want by his own.
Currently, the web application in Nextjs is pretty static, all the pages and conntent are hard coded wroten.
All my data are in JSON files and such are the images in the website.
Yes! This is a pretty hot topic right now, and there are many ways to accomplish it.
Here are the general guidelines:
Set up a "headless CMS" - this can be WordPress (set up in a special way so you are using just the backend) - or there are many other popular options, such as Contentful, Sanity, Prismic...
Your CMS needs to have an API for Next.js to use. If you go with WordPress, you can use the built-in REST API - or you can use the WP GraphQL plugin
This is such a popular topic, that if you search around, you'll find many helpful guides that go into more detail. You'll want to search "Next.JS with WordPress headless CMS"
Here's one example I found that uses GraphQL and looks fairly thorough.
Or, if you're not set on WordPress, check out Next.js-specific information for other popular headless CMS's - most of them will have specific documentation and guides for Next.JS - for example Sanity's Next.JS Guides.
WordPress is solid and flexible - but if you're not already a fairly strong WP developer, then I might recommend going with one of the more pre-packaged options (like Sanity, Prismic, Contentful, etc.) - many of them have a free tier.
I tried to use one plugin called "WP Data Sync". I am also going through its documentation/ support for the same. I am also having wpbakery page builder in my website. So is there any way that we sync with that also?
Note - We have to sync data in the form of images, image gallery, events listing, and the blog posts.
Did you check out WP Data Syncs website at https://wpdatasync.com/ and create an account to check out an API key?
I'm not sure about all APIs, but the ones I've used in the past would require me to register with the API's website, get issued an API key and maybe even designate the key to a specific website (your WordPress site in this case) for security reasons. After that, you would then go to your WP site and setup the API there via WP DataSyncs plugin.
I hope I understood your question and that this helps.
Apologies if this is the wrong place to ask and if it is, please do let me know where best to do so.
I want to write a script that will pull data from website B (external site, not owned by myself) and display that data on website A (site owned by myself).
Now, I know how to do this programmatically and so my question is more about the legalities of the approach.
For example, Twitter provides API access so that you can embed tweets or a twitter feed into your page. The sites that I would like to pull data from may or may not have such APIs and so I would have to write a scraper.
Am I allowed to scrape information from websites and display it on my own site? I will of course make it absolutely clear where the information has come from; I do not intend to use any information and claim that is is my own.
I think this is generally frowned upon, as you are basically doing the same as copying a CD putting your own label on it and selling it to others (i.e. taking someone else's stuff and pretending it's your own). I suppose it depends on the licence of the web site you are scraping. If the web site provides an API (like Twitter), then they probably allow copying.
I would like to make a streaming store like Lynda.com, Udemy.com, or other video-training websites - where the customer can buy and/or subscribe to my digital library, but the customer can only stream the content, no downloading. Is this something I should do in WordPress, Shopify, or something else? A key aspect would be the customer being able to go back-and-forth between buying an individual stream and a monthly subscription without losing their purchased streams.
The content will be self-created audio files. As far as the audio-player, I was thinking about using SoundCloud.com and privatizing the audio on SoundCloud.com. Then embed the audio onto the site to prevent pirating and rely on a third-party site to host the audio content rather than burdening the hosting provider. Or is there a better solution?
Thanks for any feedback!
You CAN use Wordpress, but there will need to be more involved then just setting up a basic website. You'll need to provide the user with a unique URL to stream the content from.
Other than building a custom platform, you can use something like http://buddypress.org/ to create user profiles. And only allow paid users to access certain content.
Shopify will only help with taking orders. Not giving users account access to login.
You could use shopify, then build out a user login side using something like Heroku. We had a similar goal to build a marketplace for live music bookings - basically the difference here being that the artists were the users, not the customers. We used Collections as profiles and Products as bookable packages. We simply embedded youtube vids and made sure to turn off recommendations in the youtube embed code. We currently make this information public, but it could be behind a login (the basic login/account that shopify provide) in your instance. It would be a little bit manual: e.g. they 'purchase' the subscription, then they create a login at checkout, whereby they're then able to access the videos/audio.
Have a play with our marketplace as an example of what I mean: tremolo.com.au
Is there any SEO disadvantage in using a subdomain to host a blog on Wordpress or Blogger? I don't want to go to the trouble of creating a blog module for my site - I'd rather just set up a CNAME entry and point a subdomain to a free Wordpress or Blogger account. Will Google punish me for doing this by claiming that I have "duplicate content" - i.e. the intro text for each blog entry will be on my main site and the full details will be visible on Wordpress/Blogger? Is it better to incorporate the blog functionality into my main site? Are there any other potential disadvantages to this subdomain/external hosting approach using a free blog host?
There are a lot of advantages to self-hosting your blog.
You can do whatever you want with your own self-hosted blog. On Wordpress you could get banned and lose all of your content.
You can host ads or and do other commercial stuff not possible on Wordpress. (The free wordpress blog doesn't allow any advertisements other than their own ads).
Better ranking opportunity in search engines by using your own top-level domain.
You can modify your functionality at will.
It looks more professional and gives you bragging rights.
On Wordpress you may run up against bandwidth restrictions if your blog gets really popular - you won't be able to do anything about it.
Willem Obst answer makes some excellent points, but two serious accusations that are not correct. I know these are incorrect because I am part of the WordPress.com team.
Num 1. If there is a ToS issue, we work with our customers to resolve the issue. In the rare case, where a blog is suspended, the customer is still assisted with exporting their content.
Num 6.We have no bandwidth limits and never have.
Many companies use free WordPress.com for their blog. Here are some examples
http://wordpress.org/showcase/flavor/wordpresscom/
WordPress.com is also is a blogging community which gives you access to a large audience and the community features like the global tag pages.
It's a great way to get a blog going, and there is no lock in. Here is an example of a blog by some friends that started on WordPress.com and since moved to host it themselves to gain the additional flexibility Willem describes so well:
http://blog.bootuplabs.com/
Finally to the original question. It's a mixed bag.
The nay sayers to using a subdomain will focus on Google and other search engines generally treating the subdomain as it's own domain with it's own authority.
The pro subdomainers will focus on it being another opportunity for a result in Google and the search engines. As is the case for the "bootup labs" example. (Although, Google's Matt Cutts over a year ago promised this was changing.)
Unrelated to SEO, many teams use a subdomain or separate domain all together for web security reasons. You may notice that http://blog.flickr.net/ is on flickr.net instead of flickr.com primarily -- I understand -- for this reason.
No in one word
Actually a good idea. Self hosted blogs tend to have a lot integrated into them e.g autopinging
In answer to the question.... NO.
The question you asked is also a little ambiguous. Are you wanting to host your own blog ie run it on your own server under a subdomain, or are you wanting to add a CNAME entry that links to your blog.
There are benefits to both:
Running your own - Advantages:
You can control every aspect of it
You can change the design/layout as much as your coding ability can handle
If you have a fast server, your blog will be served to viewers extremely well
You can advertise on your own blog - Google Adwords/Adsense etc...
You can setup advanced analysis of traffic and see every little detail about everyone who visits your blog
You can tweak the SEO of your blog to the 'n'th degree
Running your own - Disdvantages:
Hosting a blog (especially a popular one) requires a pretty powerful web server
You have to maintain the blog and security of the blog eg. users and permissions
Dedicated Server hosting can be expensive
Hosting blogs use a lot of bandwidth
Using a third party blog - Advantages:
Generally free
No strain on your server/bandwidth
Security and permissions management is limited but managed by the host
Generally hosted blogs have an extremely user-friendly GUI
Using a third party blog - Disvantages:
Sometimes include advertising that benefits the host not your company/blog
Very limited ability to customise/edit the design of the blog
Limited control over the security and user management
Other hosts can choose to stop offering a blog hosting service
In regards to SEO and blogs:
Your blog is not going to suffer or be penalised by GOogle/Yahoo/Other search engines if you use a CNAME redirection to another host.
You will not get penalised by a search engine for duplicate content if the content is not completely duplicated on, for example if your main domain uses the title and summary of what is on your blog hosted on the subdomain.
If you adhere to the main SEO principles there is no reason why your blog would suffer on a subdomain:
Using relevant addressing methods eg. yourblog.yourdomain.com/title-of-blog-article.html
Use W3C compliant/correct XHTML/HTML/CSS code
Use appropriate and relevant META data (keywords, descriptions, titles) for the blog and the articles.
Relative linking instead of absolute linking
Hope this helped. If you have any other questions feel free to ask