Is the Sprint Goal is a part of Sprint Backlog?

Typo correction:

Though the Scrum guide doesn't specify so, I have read in few articles that "the Sprint Goal is a part of Sprint Backlog". My understanding is that this is not the case as Sprint Backlog is ever changing throughout the Sprint while the Sprint goal is an objective to be met and not something actionable to form a part of the Sprint Backlog.

Would it help to include the Sprint Goal in the Sprint Backlog? Would doing so improve transparency, for example?

I have read in few articles that "the Sprint Goal is a part of Sprint Backlog".

It's an ambiguous statement. What do the authors of those articles mean? It could simply be down to the level of English being used by those authors, or it could be a lack of understanding of Scrum.

I would say no, they're separate things, but there is a relation. The Sprint Backlog should contain a plan for achieving the Sprint Goal. That plan for achieving the Sprint Goal can be adapted by the Development Team at any time, whereas the Sprint Goal itself cannot be adapted. It can only be replaced if the Product Owner cancels the Sprint.

Inherently it is: since the sprint backlog contains (at least) the work to be Done for achieving it.

But these are two different concepts.

Sprint goals are the burning torch for the team. It give guidance and purpose to the work they are doing.

Therefore having a clear sprint goal, and giving it a prominent position can help.

I would not make it part of the sprint backlog itself when it comes to tracking of work. It might be confusing. But you can make the sprint title the same as the sprint goal, you can print it on a big poster and hang it on the wall, you can put it on the monitors, whatever. There are a lot of ways to visualize the sprint goal. And every Daily Scrum you can look at the poster and give updates related to that phrase

Thanks that clarifies.

If I were to use a life example where my Sprint goal is to be able to drive a car by a certain date, my Sprint Backlog would contain all the things I need to do to be able to meet my objective. I could add / remove various items from the Sprint Backlog as I ascertain better ways to reach my goal, given the Sprint Backlog can be adapted as more is learnt. However, if my Sprint goal changes to being able to swim by a certain date, the existing Sprint Backlog serves no meaning. Making the the Sprint goal a part of the Sprint Backlog gives the impression that the Sprint goal can be changed as well which cannot be the case for a Sprint in progress. 

There seems to be ambiguity in the way sometimes some authors construct the sentences that could in essence change the whole meaning. Grateful to the experienced people on this forum who take the time to pass on their knowledge. 

I'm so lost with this question.

from Scrum Guide 2020: 
https://scrumguides.org/scrum-guide.html#sprint-backlog

The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).

and later:
The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog

and to answer to the comment that one is changing while the other is not:

If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal

The responses to the question were before the 2020 revision of the Scrum Guide were released.  The 2020 version of the Scrum Guide was released on November 18, 2020.